Triple
T26428620
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulam tribe |
E664438
|
entity |
| Predicate | primaryResourceSought |
P196071
|
FINISHED |
| Object | fire |
—
|
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: fire | Statement: [Ulam tribe, primaryResourceSought, fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryResourceSought Context triple: [Ulam tribe, primaryResourceSought, fire]
-
A.
primaryResourceType
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
B.
primaryTarget
Indicates that an entity is the main or most important target of another entity’s action, focus, or effect.
-
C.
primaryTargetType
Indicates the main category or type of entity that is the principal focus or intended recipient of an action, effect, or operation.
-
D.
primarySingle
Indicates that an entity has exactly one main or primary association of the specified type, with no additional concurrent primary associations.
-
E.
primaryFor
Indicates that one entity serves as the main or principal option, resource, or association for another entity among possible alternatives.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
| PDg | Predicate description generation | batch_69fe066b623c819085205fbea901e3cf |
completed | May 8, 2026, 3:51 p.m. |
Created at: April 26, 2026, 11:47 p.m.