Triple
T6113554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tepanec |
E136303
|
entity |
| Predicate | dominantUntil |
P68222
|
FINISHED |
| Object | 15th century |
—
|
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: 15th century | Statement: [Tepanec, dominantUntil, 15th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dominantUntil Context triple: [Tepanec, dominantUntil, 15th century]
-
A.
dominantDuring
Indicates that one entity holds a prevailing or controlling influence over another specifically within a given time period or interval.
-
B.
dominantOn
Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
-
C.
dominatesSince
Indicates that one entity has maintained a position of dominance or control over another entity continuously from a specified starting time onward.
-
D.
dominatedBy
Indicates that one entity is under the control, influence, or overpowering authority of another entity.
-
E.
dominantTree
Indicates that one tree has a dominant or prevailing influence over another tree, such as in size, canopy coverage, or competitive advantage within a shared environment.
- 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bbf2ee4819097af2cce9248bf4e |
completed | March 22, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:14 p.m.