Triple
T23067878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stheno |
E575101
|
entity |
| Predicate | homeInSomeAccounts |
P104753
|
FINISHED |
| Object | farWesternEdgeOfTheWorld |
—
|
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: farWesternEdgeOfTheWorld | Statement: [Stheno, homeInSomeAccounts, farWesternEdgeOfTheWorld]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeInSomeAccounts Context triple: [Stheno, homeInSomeAccounts, farWesternEdgeOfTheWorld]
-
A.
hasHome
chosen
Indicates that an entity possesses or is associated with a place where it lives or is based.
-
B.
primaryAccountIn
Indicates that an entity serves as the main or default account within a specified context, group, or container.
-
C.
homeTo
Indicates that a place serves as the primary location, residence, or habitat for a person, group, or thing.
-
D.
homeManager
Indicates that one entity manages, oversees, or is responsible for the operations or affairs of another entity’s home or household.
-
E.
homeRecord
Indicates the record or statistics associated with an entity’s performance or activity in its home context or location.
- 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_69e245bd6e4c8190bb8942245b68cad5 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f189a5aa4081909b3f0dc92877323d |
completed | April 29, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
Created at: April 17, 2026, 3:55 p.m.