Triple
T6785936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonial City of Santo Domingo |
E155801
|
entity |
| Predicate | hasOldest |
P7751
|
FINISHED |
| Object | oldest cathedral in the Americas |
—
|
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: oldest cathedral in the Americas | Statement: [Colonial City of Santo Domingo, hasOldest, oldest cathedral in the Americas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOldest Context triple: [Colonial City of Santo Domingo, hasOldest, oldest cathedral in the Americas]
-
A.
isOldest
chosen
Indicates that one entity has a greater age than all other relevant entities in the comparison set.
-
B.
isOldestOrderOf
Indicates that one order is the earliest or first created among a set of related orders for a given context or entity.
-
C.
isOldestLineOf
Indicates that one line is the earliest or first-established among a set of related lines.
-
D.
isOldestMajor
Indicates that the subject is the oldest entity among a specified group that meets a defined age or maturity threshold.
-
E.
oldestStatus
Indicates that the associated status is the earliest or longest-standing one in a sequence of statuses for an entity.
- 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_69c6881770fc8190972b2906390380f5 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d28f043081909a9a9ab635785933 |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d0979ce0819094678896da4e3169 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.