Triple
T34989180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prydwen |
E1009333
|
entity |
| Predicate | homeBaseFor |
P25972
|
FINISHED |
| Object | Elder Arthur Maxson |
—
|
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: Elder Arthur Maxson | Statement: [Prydwen, homeBaseFor, Elder Arthur Maxson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeBaseFor Context triple: [Prydwen, homeBaseFor, Elder Arthur Maxson]
-
A.
homeBaseOf
chosen
Indicates that a particular place serves as the primary location, headquarters, or main operational base for an entity.
-
B.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
C.
isResidentialBaseFor
Indicates that a location serves as the primary place of residence or home base for a person or group.
-
D.
homeGroundFrom
Indicates that an entity serves as the home ground or primary venue for another entity (such as a team or organization).
-
E.
earlyHomeVenueFor
Indicates that one entity served as the primary home venue for another entity during an early or initial period of its existence or activity.
- 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_69f76dca50dc8190b71f39defe186be8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4:01 p.m.