Triple
T29468173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Site 1 |
E747436
|
entity |
| Predicate | launchDateOfNotableEvent |
P180
|
FINISHED |
| Object | 1961-04-12 |
—
|
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: 1961-04-12 | Statement: [Site 1, launchDateOfNotableEvent, 1961-04-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchDateOfNotableEvent Context triple: [Site 1, launchDateOfNotableEvent, 1961-04-12]
-
A.
notableEventDate
Indicates the date on which a notable or significant event associated with the subject occurred.
-
B.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
C.
notableEventTime
Indicates the specific time at which a notable or significant event occurred.
-
D.
launchDate
chosen
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
E.
launchDateNote
Indicates a note or qualifier providing additional information or context about an entity’s launch date.
- 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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 28, 2026, 3:55 p.m.