Triple
T13986096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICE in-flight entertainment system |
E336444
|
entity |
| Predicate | contentUpdated |
P71451
|
FINISHED |
| Object | regularly |
—
|
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: regularly | Statement: [ICE in-flight entertainment system, contentUpdated, regularly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentUpdated Context triple: [ICE in-flight entertainment system, contentUpdated, regularly]
-
A.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
B.
updatedIn
Indicates that an entity has undergone a change or modification within a specified time period or version context.
-
C.
updatedEvery
chosen
Indicates that something is refreshed or brought up to date at a regular, specified interval.
-
D.
isUpdated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or a reference point.
-
E.
editedIn
Indicates that an entity was modified, revised, or otherwise altered within a particular context, tool, environment, or time frame.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ea3e5a081908ed8ead108139252 |
completed | April 14, 2026, 12:10 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.