Triple
T38215104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinagua people |
E1010662
|
entity |
| Predicate | mayHaveMergedInto |
P50684
|
FINISHED |
| Object | Hopi people |
—
|
NE NERFINISHED |
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: Hopi people | Statement: [Sinagua people, mayHaveMergedInto, Hopi people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHaveMergedInto Context triple: [Sinagua people, mayHaveMergedInto, Hopi people]
-
A.
laterMergedWith
Indicates that one entity was combined into and became part of another entity at a subsequent point in time.
-
B.
hasMerger
Indicates a relationship where two or more entities combine into a single entity through a merger event.
-
C.
someMembersMergedWith
chosen
Indicates that a subset of members from one group combined or integrated with members of another group to form a unified entity or subgroup.
-
D.
intendedToMerge
Indicates that one entity had the purpose or plan to combine or consolidate with another entity into a single unit.
-
E.
canMerge
Indicates that two or more entities are compatible in such a way that they can be combined into a single unified entity or structure.
- F. None of above.
Provenance (3 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.