Triple
T7402887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mon Paris |
E170790
|
entity |
| Predicate | suitableOccasion |
P76573
|
FINISHED |
| Object | evening wear |
—
|
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: evening wear | Statement: [Mon Paris, suitableOccasion, evening wear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suitableOccasion Context triple: [Mon Paris, suitableOccasion, evening wear]
-
A.
displayOccasion
Indicates the event, context, or situation during which something is presented, shown, or made visible.
-
B.
entryOccasion
Indicates the circumstance, event, or reason that prompts or justifies an entity’s entry or initiation.
-
C.
specialOccasion
Indicates that an event or situation is associated with a notable or exceptional occasion, such as a celebration, milestone, or culturally significant date.
-
D.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
E.
premiereOccasion
Indicates the event or context in which something (such as a work, show, or product) is first publicly presented or launched.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26ea27c8190a55e0e0314b463d8 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f0323b2c819098ab72c33e6d8534 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f15c36d48190bc75353d3f67555a |
completed | March 27, 2026, 9:06 p.m. |
Created at: March 27, 2026, 3:10 p.m.