Triple
T14182607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navigate Your Stars |
E351492
|
entity |
| Predicate | settingOfDelivery |
P85353
|
FINISHED |
| Object | commencement ceremony |
—
|
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: commencement ceremony | Statement: [Navigate Your Stars, settingOfDelivery, commencement ceremony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfDelivery Context triple: [Navigate Your Stars, settingOfDelivery, commencement ceremony]
-
A.
deliverySystem
Indicates a system, method, or mechanism by which something (such as a product, service, or substance) is transported, distributed, or conveyed from a source to a recipient.
-
B.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
C.
deliveryStyle
Indicates the manner or approach with which something (such as information, a product, or a service) is presented, communicated, or provided to its recipient.
-
D.
deliveryStandard
Indicates the agreed level, method, or timeframe by which a delivery is to be carried out between parties.
-
E.
locationOfDelivery
chosen
Indicates the place or address where an item, service, or shipment is to be delivered.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61cc0a848190b660095972b1223b |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:02 a.m.