Triple
T15187632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exit C |
E362917
|
entity |
| Predicate | exitLetter |
P117052
|
FINISHED |
| Object | C |
—
|
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: C | Statement: [Exit C, exitLetter, C]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exitLetter Context triple: [Exit C, exitLetter, C]
-
A.
extensionLetter
Indicates that a formal letter has been issued granting an extension of time or deadline for an existing obligation, agreement, or process.
-
B.
leaveType
Indicates the type or category of leave associated with an absence or time-off event (e.g., vacation, sick leave, parental leave).
-
C.
leaveProtection
Indicates that an entity stops providing protection or removes a protective status from another entity.
-
D.
exitTo
Indicates that one location or entity serves as a passage or route leading directly to another location or entity.
-
E.
canResign
Indicates that an entity has the authority or option to voluntarily leave a position, role, or membership.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e0067995fc8190b048f15086bd42f0 |
completed | April 15, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:09 a.m.