Triple
T3981475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelantado mayor |
E85767
|
entity |
| Predicate | exercisedOver |
P6502
|
FINISHED |
| Object | designated territory |
—
|
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: designated territory | Statement: [Adelantado mayor, exercisedOver, designated territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisedOver Context triple: [Adelantado mayor, exercisedOver, designated territory]
-
A.
exercisedPowerOver
chosen
Indicates that one entity exerted control, influence, or authority over another entity.
-
B.
overcameHoldingOf
Indicates that one entity successfully defeated, reversed, or nullified another entity’s control, possession, or dominance over something.
-
C.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
-
D.
holdsOver
Indicates that a certain condition, state, or relationship remains valid or continues to apply across a specified period, context, or range.
-
E.
overtook
Indicates that one entity moved past and ahead of another that was previously in front, typically while both were in motion.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefa3ef7ac8190abe02f440ff83c43 |
completed | March 9, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69aef8f492ac819089dbb9436dbcdd2b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.