Triple
T37225219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orbit City |
E922987
|
entity |
| Predicate | employerLocatedIn |
P10544
|
FINISHED |
| Object | Spacely Space Sprockets |
—
|
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: Spacely Space Sprockets | Statement: [Orbit City, employerLocatedIn, Spacely Space Sprockets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: employerLocatedIn Context triple: [Orbit City, employerLocatedIn, Spacely Space Sprockets]
-
A.
organizationLocatedAt
Indicates that an organization is situated or based at a specific geographic location or address.
-
B.
recruitmentLocation
Indicates the place or geographic area where the recruitment or hiring of individuals occurs.
-
C.
agencyLocatedIn
Indicates that an agency is situated or based within a specific geographic or administrative location.
-
D.
isTypicallyBasedIn
Indicates that one entity is most commonly located, headquartered, or primarily operates within the context or place specified by another entity.
-
E.
employerHeadquarters
chosen
Indicates the location where an employer’s main corporate offices or central administrative operations are based.
- 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_69f76ea7f0008190b31b8e30f3d05a71 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
Created at: May 3, 2026, 4:15 p.m.