Triple
T37507660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ring of Fates |
E932138
|
entity |
| Predicate | factionAccessibility |
P190019
|
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: [Ring of Fates, factionAccessibility, Alliance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: factionAccessibility Context triple: [Ring of Fates, factionAccessibility, Alliance]
-
A.
visitorAccessibility
Indicates how easily or suitably a place, service, or resource can be used or reached by visitors, including those with varying needs or abilities.
-
B.
cultAccessibility
chosen
Indicates how easily a cult can be approached, joined, or engaged with by individuals or groups.
-
C.
accessibleFrom
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
D.
isDifficultToAccess
Indicates that reaching, using, or obtaining the referenced entity requires significant effort, obstacles, or special conditions.
-
E.
accessArea
Indicates that an entity is permitted to enter, use, or interact with a specified physical or logical area.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:17 p.m.