Triple
T38590603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gridania |
E932443
|
entity |
| Predicate | homeToOrganization |
P25972
|
FINISHED |
| Object | Order of the Twin Adder |
—
|
NE NERFINISHED |
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: Order of the Twin Adder | Statement: [Gridania, homeToOrganization, Order of the Twin Adder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeToOrganization Context triple: [Gridania, homeToOrganization, Order of the Twin Adder]
-
A.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
B.
hostOrganizationFor
Indicates that one organization serves as the hosting or organizing body responsible for an event, activity, or program involving another entity.
-
C.
toOrganization
Indicates a relationship where something or someone is directed, transferred, or associated toward a specific organization as the destination or target.
-
D.
leftOrganization
Indicates that an entity has departed from or is no longer affiliated with a particular organization.
-
E.
homeBaseOf
chosen
Indicates that a particular place serves as the primary location, headquarters, or main operational base for an entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.