Triple
T27343353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise (OV-101) |
E684167
|
entity |
| Predicate | publicUnveiling |
P138710
|
FINISHED |
| Object | 1976-09-17 |
—
|
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: 1976-09-17 | Statement: [Enterprise (OV-101), publicUnveiling, 1976-09-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicUnveiling Context triple: [Enterprise (OV-101), publicUnveiling, 1976-09-17]
-
A.
officialUnveiling
chosen
Indicates a formal, often ceremonial, public presentation or introduction of something (such as an object, project, or initiative) by an authorized party.
-
B.
unveiledWith
Indicates that one entity is revealed, introduced, or made public at the same time as, and in conjunction with, another entity.
-
C.
unveiledAs
Indicates that one entity is revealed, presented, or disclosed in the role, identity, or form of another entity.
-
D.
secretRevealed
Indicates that previously hidden or confidential information has been disclosed to one or more parties.
-
E.
secretRevealedThrough
Indicates that a secret becomes known or disclosed by means of a specified channel, method, or intermediary.
- 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_69ef1480a76481908684256ddd5bfda3 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f7805ce6208190ac6dbd9c97989978 |
completed | May 3, 2026, 5:05 p.m. |
| PD | Predicate disambiguation | batch_69f77956ec648190ba4fb7e9d83fd107 |
completed | May 3, 2026, 4:35 p.m. |
Created at: April 27, 2026, 11:44 a.m.