Triple
T16853048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | webOS |
E409720
|
entity |
| Predicate | acquisitionDateByLG |
P2754
|
FINISHED |
| Object | 2013-02-25 |
—
|
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: 2013-02-25 | Statement: [webOS, acquisitionDateByLG, 2013-02-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acquisitionDateByLG Context triple: [webOS, acquisitionDateByLG, 2013-02-25]
-
A.
acquisitionDate
chosen
Indicates the date on which one entity formally acquires or takes ownership of another entity.
-
B.
GSAAscertainmentDate
Indicates the date on which the General Services Administration (GSA) formally determines and certifies the outcome or status relevant to the referenced process or event.
-
C.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
-
D.
acquisitionCompletedYear
Indicates the calendar year in which an acquisition transaction was fully completed.
-
E.
retrievalDate
Indicates the date on which an item, record, or resource was accessed, obtained, or retrieved.
- 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_69d88395e6c88190b22730f335107c14 |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b37abadc81909d02d329403497d6 |
completed | April 18, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69e32b8cbb048190878a259cc5be960e |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:24 a.m.