Triple
T17960802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ODI |
E449074
|
entity |
| Predicate | dayNightMatchesAllowed |
P129906
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ODI, dayNightMatchesAllowed, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dayNightMatchesAllowed Context triple: [ODI, dayNightMatchesAllowed, yes]
-
A.
dayNightMatches
Indicates that two time-related entities correspond in terms of being in the same phase of the day–night cycle (e.g., both are during daytime or both are during nighttime).
-
B.
dayNightVariant
Indicates a relationship where one entity is a day-time version and the other is a night-time version of the same underlying thing.
-
C.
associatedNightTiming
Indicates a relationship where an event, action, or condition is linked specifically to a time period occurring during the night.
-
D.
darkMatch
Indicates a relationship where two entities are matched or aligned in a hidden, non-public, or preliminary context not visible in the main or standard view.
-
E.
isIlluminatedAtNight
Indicates that an entity receives or emits sufficient light to be visibly illuminated during nighttime conditions.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b131fa8481908cd756f350eb6359 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
| PDg | Predicate description generation | batch_69e42d8d68288190a05dc5d7803cf823 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:22 a.m.