Triple
T36269823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitad del Mundo |
E892638
|
entity |
| Predicate | hasMonumentTopFeature |
P127363
|
FINISHED |
| Object | metal globe |
—
|
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: metal globe | Statement: [Mitad del Mundo, hasMonumentTopFeature, metal globe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMonumentTopFeature Context triple: [Mitad del Mundo, hasMonumentTopFeature, metal globe]
-
A.
hasMonumentalFeature
chosen
Indicates that an entity possesses or includes a significant, large-scale, or historically important physical feature or structure.
-
B.
hasMonumentFunction
Indicates that something serves the role or purpose of a monument, such as commemorating, honoring, or symbolizing a person, event, or idea.
-
C.
hasPrimaryMonument
Indicates that an entity is associated with its main or most significant monument.
-
D.
hasMonumentAt
Indicates that a monument is located at or associated with a specific place or site.
-
E.
hasMonumentalPresence
Indicates that an entity possesses a grand, imposing, or highly impactful presence in its context or environment.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff4de66ba481908e7184b3cf9d4d2d |
completed | May 9, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69ff4c702a5881909c6684c74807e945 |
completed | May 9, 2026, 3:02 p.m. |
Created at: May 3, 2026, 4:09 p.m.