Triple
T11547733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sepulcher of the First Ones |
E273812
|
entity |
| Predicate | factionAccess |
P2942
|
FINISHED |
| Object | Alliance |
—
|
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: Alliance | Statement: [Sepulcher of the First Ones, factionAccess, Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionAccess Context triple: [Sepulcher of the First Ones, factionAccess, Alliance]
-
A.
factionRole
Indicates the specific role, function, or position an entity holds within a particular faction or group.
-
B.
crewAccess
Indicates that one entity has permission or authorization to access or enter an area, resource, or function reserved for crew members.
-
C.
faction
chosen
Indicates that an entity is formally affiliated with, or belongs to, a particular faction or organized group within a broader context.
-
D.
factionSystem
Indicates a relationship where a faction is associated with, operates within, or controls a particular system (such as a region, domain, or organizational structure).
-
E.
factionSymbol
Indicates the specific faction with which an entity is associated or aligned.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e615b08190a072924329a94a6a |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.