Triple
T36822022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlacomulco |
E909909
|
entity |
| Predicate | hasNotableAssociatedGroup |
P26016
|
FINISHED |
| Object | Grupo Atlacomulco |
E2199355
|
NE 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: Grupo Atlacomulco | Statement: [Atlacomulco, hasNotableAssociatedGroup, Grupo Atlacomulco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAssociatedGroup Context triple: [Atlacomulco, hasNotableAssociatedGroup, Grupo Atlacomulco]
-
A.
hasNotableRelativeGroup
Indicates that an entity is associated with a group of relatives who are notable or significant in some recognized way.
-
B.
hasNotableRecipientGroup
Indicates that an entity is associated with a specific group that is recognized as a notable or distinguished recipient of something (e.g., an award, benefit, or honor).
-
C.
hasRelatedGroup
chosen
Indicates that one group or collection is associated with another group or collection through some defined relationship or connection.
-
D.
hasNotableGroupCharacteristic
Indicates that a group possesses a distinctive or noteworthy characteristic that sets it apart from other groups.
-
E.
hasNotableLocationAssociation
Indicates that there is a significant or noteworthy connection between an entity and a specific location.
- F. None of above.
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_69f76e7dd13c81908c60b05adb49eeb5 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3dfad26bb0819097980dee3e90ec50 |
completed | June 26, 2026, 4:06 a.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.