Triple
T35748015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B.zero1 |
E1033239
|
entity |
| Predicate | launchedToMark |
P185698
|
FINISHED |
| Object | new millennium |
—
|
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: new millennium | Statement: [B.zero1, launchedToMark, new millennium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedToMark Context triple: [B.zero1, launchedToMark, new millennium]
-
A.
launchedTo
Indicates that one entity has been sent or propelled from its origin toward a specific target or destination.
-
B.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
C.
builtToMark
Indicates that something was constructed for the purpose of commemorating, signaling, or designating a particular event, place, boundary, or significance.
-
D.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
-
E.
launchesTo
Indicates that one entity initiates the sending or propulsion of another entity toward a specific destination or into a particular trajectory.
- 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_69f76e119d508190a3873cb302063832 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: May 3, 2026, 4:06 p.m.