Triple
T29684318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TH-73A Thrasher |
E751040
|
entity |
| Predicate | intendedToServeUntil |
P184602
|
FINISHED |
| Object | around 2050s |
—
|
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: around 2050s | Statement: [TH-73A Thrasher, intendedToServeUntil, around 2050s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedToServeUntil Context triple: [TH-73A Thrasher, intendedToServeUntil, around 2050s]
-
A.
servedUntil
Indicates the ending time or date up to which an entity held a position, role, or service.
-
B.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
C.
operatedUntil
Indicates that an entity continued to function or be in operation up to a specified end time or date.
-
D.
tookPlaceUntil
Indicates that an event or situation occurred continuously or repeatedly up to a specified end time or date, after which it no longer took place.
-
E.
maintainedUntil
Indicates that a state, condition, or relationship continues to hold true up to a specified endpoint in time, but not necessarily beyond it.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: April 28, 2026, 7:12 p.m.