Triple
T20250960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ExpressJet Airlines |
E498552
|
entity |
| Predicate | operatedIndependentServicePeriod |
P802
|
FINISHED |
| Object | mid-2000s |
—
|
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: mid-2000s | Statement: [ExpressJet Airlines, operatedIndependentServicePeriod, mid-2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedIndependentServicePeriod Context triple: [ExpressJet Airlines, operatedIndependentServicePeriod, mid-2000s]
-
A.
operatedDuring
chosen
Indicates that an action, process, or system was functioning or in operation throughout a specified time period or event.
-
B.
serviceEntryPeriod
Indicates the span of time during which a service is active, valid, or in effect for the related entities.
-
C.
servedByTimePeriod
Indicates that a service, event, or activity occurs or is provided during a specified time period.
-
D.
serviceOpenedBetween
Indicates that a service has been initiated or made available during the time interval between two specified points or events.
-
E.
primaryServicePeriod
Indicates the main or most significant span of time during which a service, duty, or activity is performed or in effect.
- 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_69da6274c58c81909c646eabed6f4f30 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e673a79a208190a5a7c0f6515bc393 |
completed | April 20, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69e55b1b23f88190bdcbe2f81dd226dd |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:41 p.m.