Triple
T34026130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | go card |
E872510
|
entity |
| Predicate | launchedToPublic |
P8763
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [go card, launchedToPublic, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedToPublic Context triple: [go card, launchedToPublic, 2008]
-
A.
launchedTo
Indicates that one entity has been sent or propelled from its origin toward a specific target or destination.
-
B.
becamePublic
Indicates that an entity transitioned from private or restricted status to being publicly accessible or publicly traded.
-
C.
madePublicAfter
Indicates that one entity was made publicly accessible only after the occurrence or completion of another specified entity or event.
-
D.
openedToPublicBy
Indicates that an entity was made accessible or available to the general public through the action or decision of another entity.
-
E.
launchedAt
chosen
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
- 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_69f349a2527c81909a7cd4bda94d70ad |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:51 a.m.