Triple
T3147714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxygen |
E65802
|
entity |
| Predicate | originalLaunch |
P7203
|
FINISHED |
| Object | February 2, 2000 |
—
|
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: February 2, 2000 | Statement: [Oxygen, originalLaunch, February 2, 2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalLaunch Context triple: [Oxygen, originalLaunch, February 2, 2000]
-
A.
originalRelease
Indicates the initial publication or first official release event of a work or product.
-
B.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
C.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
D.
firstSuccessfulLaunchDate
chosen
Indicates the calendar date on which an entity achieved its first successful launch.
-
E.
originallyReleasedOn
Indicates the date or platform on which something (such as a work, product, or media item) was first made publicly available.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59a54188190a2e020fd4004d734 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.