Triple
T25226841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of the Cross (Palenque) |
E632107
|
entity |
| Predicate | hasGroupRole |
P161
|
FINISHED |
| Object | principal temple of the Cross Group |
—
|
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: principal temple of the Cross Group | Statement: [Temple of the Cross (Palenque), hasGroupRole, principal temple of the Cross Group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGroupRole Context triple: [Temple of the Cross (Palenque), hasGroupRole, principal temple of the Cross Group]
-
A.
hasGroupMember
Indicates that a group or collection includes a specific entity as one of its members.
-
B.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
-
C.
hasGalaxyGroupRole
Indicates that an entity holds a specific role or function within a galaxy group.
-
D.
hasRole
chosen
Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
-
E.
hasSubsidiaryRoleInGroup
Indicates that an entity holds a secondary or supporting role within a specified group.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47cc42b808190977730a9ec2de79c |
completed | May 1, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:04 p.m.