Triple
T36954305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Athena’s Fortune |
E914149
|
entity |
| Predicate | hideoutAccessibleFrom |
P1985
|
FINISHED |
| Object | Tavern in any Outpost |
—
|
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: Tavern in any Outpost | Statement: [Athena’s Fortune, hideoutAccessibleFrom, Tavern in any Outpost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hideoutAccessibleFrom Context triple: [Athena’s Fortune, hideoutAccessibleFrom, Tavern in any Outpost]
-
A.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
B.
accessibleFrom
chosen
Indicates that one entity can be reached, entered, or used starting from another entity, typically without obstruction.
-
C.
accessibleExit
Indicates that an exit is designed and configured to be usable by people with disabilities, meeting accessibility requirements.
-
D.
hasDomeOrRoofAccess
Indicates that an entity has access to, or the ability to reach or use, a dome or roof area associated with another entity.
-
E.
hasTypicalAtticAccess
Indicates that an entity has a standard or commonly used means of accessing an attic space.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.