Triple
T37235109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monaco |
E923550
|
entity |
| Predicate | launchedInitialCoinOfferingIn |
P192407
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Monaco, launchedInitialCoinOfferingIn, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchedInitialCoinOfferingIn Context triple: [Monaco, launchedInitialCoinOfferingIn, 2017]
-
A.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
B.
launchedFirstUnit
Indicates that one entity initiated and deployed the first unit of something (e.g., product, system, or mission) before any others.
-
C.
launchedWithSponsor
Indicates that an entity was initiated, released, or started in association with a sponsoring organization or individual.
-
D.
launchedTo
Indicates that one entity has been sent or propelled from its origin toward a specific target or destination.
-
E.
launchedWith
Indicates that one entity was initiated, started, or set into motion together with another entity as part of the same launch event.
- 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_69f76ea9fee88190a589f661d95a7189 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69fd098357348190a835c0b6d99857d2 |
completed | May 7, 2026, 9:52 p.m. |
Created at: May 3, 2026, 4:15 p.m.