Triple
T37462594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyrantus |
E930954
|
entity |
| Predicate | hasTribeRole |
P51333
|
FINISHED |
| Object | Large Beast |
—
|
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: Large Beast | Statement: [Tyrantus, hasTribeRole, Large Beast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribeRole Context triple: [Tyrantus, hasTribeRole, Large Beast]
-
A.
hasNonParticipantTribe
Indicates that a tribe is associated with a situation or event but does not actively participate in it.
-
B.
hasTribalTag
Indicates that an entity is associated with, marked by, or identified through a specific tribal tag or tribal affiliation label.
-
C.
hasTribalLevel
Indicates that one entity is associated with, classified by, or assigned a particular tribal level or rank in a hierarchical tribal structure.
-
D.
hasRoleInCommunity
chosen
Indicates that an entity holds or performs a specific role, function, or position within a particular community.
-
E.
hasTribalAssociation
Indicates that an entity is affiliated with, belongs to, or is formally associated with a particular tribe or tribal 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0031ed5d708190ab93516ad081ada6 |
completed | May 10, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_6a0031b5dbd081908eb0f4dbb8a0eac3 |
completed | May 10, 2026, 7:20 a.m. |
Created at: May 3, 2026, 4:17 p.m.