Triple
T11642438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Castle Nathria |
E276689
|
entity |
| Predicate | raidSizeMode |
P100151
|
FINISHED |
| Object | flexible |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: flexible | Statement: [Castle Nathria, raidSizeMode, flexible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raidSizeMode Context triple: [Castle Nathria, raidSizeMode, flexible]
-
A.
raidSize
Indicates the number of participants or units involved in a single raid event.
-
B.
raidSizeOriginal
Indicates the original number of participants or units involved in a raid before any changes or adjustments.
-
C.
romSize
Indicates the amount of read-only memory (ROM) associated with an entity, typically measured as its storage capacity.
-
D.
ramExpandableTo
Indicates that a device’s RAM can be increased from its current capacity up to a specified maximum amount.
-
E.
raid
Indicates a sudden, targeted attack or incursion by one party into another’s domain, typically to seize assets, gather information, or cause disruption.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a260ab488190ab1c00d9850f3096 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
| PDg | Predicate description generation | batch_69d87f30642c8190ad94fa061cde186b |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.