Triple
T4495967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JetSMART |
E100695
|
entity |
| Predicate | fleetConfiguration |
P56898
|
FINISHED |
| Object | single-class cabin |
—
|
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: single-class cabin | Statement: [JetSMART, fleetConfiguration, single-class cabin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetConfiguration Context triple: [JetSMART, fleetConfiguration, single-class cabin]
-
A.
fleetCommander
Indicates that one entity serves as the commanding officer or overall leader in charge of the operations and decisions of a fleet associated with another entity.
-
B.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
C.
fleetName
Indicates the name assigned to a particular fleet within a system or context.
-
D.
fleetBase
Indicates that one entity serves as the primary homeport, headquarters, or main operating base for a fleet associated with the other entity.
-
E.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56bde14c819091d42839a46291d0 |
completed | March 20, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1 p.m.