Triple
T1656866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-107 |
E35817
|
entity |
| Predicate | reentryBreakupLocation |
P30968
|
FINISHED |
| Object | over Texas |
—
|
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: over Texas | Statement: [STS-107, reentryBreakupLocation, over Texas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryBreakupLocation Context triple: [STS-107, reentryBreakupLocation, over Texas]
-
A.
dischargeLocation
Indicates the place or facility where an entity (such as a person, object, or substance) is released, sent, or discharged to after a prior state or process.
-
B.
apseLocation
Indicates the specific place or position where an apse is situated within a larger structure or context.
-
C.
leasedFrom
Indicates that one entity is renting or leasing something from another entity, which acts as the owner or lessor.
-
D.
exileLocation
Indicates the place or destination to which an entity is sent or kept in exile.
-
E.
reunitedIn
Indicates that entities who were previously separated have come together again at a specific time or place.
- F. None of above. chosen
Provenance (4 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_69a88606aa808190aa0b421b4271f220 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a99a4c3810819089d2dd0e23c8e46b |
completed | March 5, 2026, 2:59 p.m. |
Created at: March 4, 2026, 7:29 p.m.