Triple
T34503806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arrow |
E885827
|
entity |
| Predicate | hasOccasionFocus |
P2934
|
FINISHED |
| Object | formal occasions |
—
|
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: formal occasions | Statement: [Arrow, hasOccasionFocus, formal occasions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOccasionFocus Context triple: [Arrow, hasOccasionFocus, formal occasions]
-
A.
hasOccasionType
Indicates that an occasion, event, or happening is classified as being of a particular type or category.
-
B.
targetOccasion
Indicates the specific event, situation, or occasion toward which an action, plan, or intention is directed.
-
C.
displayOccasion
chosen
Indicates the event, context, or situation during which something is presented, shown, or made visible.
-
D.
onOccasionOf
Indicates that one event, action, or state occurs in connection with, or is triggered by, a particular occasion or special event.
-
E.
entryOccasion
Indicates the circumstance, event, or reason that prompts or justifies an entity’s entry or initiation.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 2:01 a.m.