Triple
T7318972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mitla |
E168487
|
entity |
| Predicate | hasSiteGroup |
P76274
|
FINISHED |
| Object | Group of the Columns |
—
|
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: Group of the Columns | Statement: [Mitla, hasSiteGroup, Group of the Columns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteGroup Context triple: [Mitla, hasSiteGroup, Group of the Columns]
-
A.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
B.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
C.
hasSiteCode
Indicates that an entity is associated with a specific site identifier or code used to distinguish its location or facility.
-
D.
hasCentralGroup
Indicates that an entity possesses or is associated with a primary or central group within its structure or organization.
-
E.
hasStationGroup
Indicates that an entity is associated with, or belongs to, a particular group or collection of stations.
- 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_69c68a5251508190ad68df4151cfeb04 |
completed | March 27, 2026, 1:46 p.m. |
| NER | Named-entity recognition | batch_69c6ef18b7bc81908a9ee405d684f304 |
completed | March 27, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb88a2648190acc79eeee8733705 |
completed | March 27, 2026, 8:41 p.m. |
Created at: March 27, 2026, 3:02 p.m.