Triple
T647016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US Airways |
E11262
|
entity |
| Predicate | fleetSizeAtPeak |
P1848
|
FINISHED |
| Object | approximately 340 aircraft |
—
|
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: approximately 340 aircraft | Statement: [US Airways, fleetSizeAtPeak, approximately 340 aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fleetSizeAtPeak Context triple: [US Airways, fleetSizeAtPeak, approximately 340 aircraft]
-
A.
fleetSize
chosen
Indicates the total number of vehicles, vessels, or units that collectively make up a fleet associated with an entity.
-
B.
teamCountAtPeak
Indicates the number of team members involved at the highest or peak point of activity, size, or performance.
-
C.
memberCountAtPeak
Indicates the highest number of members that an entity (such as a group or organization) has had at any point in time.
-
D.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
E.
crewCountApproximate
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f1cb24481909d3b41a56b29dee9 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0c0dcc8190849211d45489a5a7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.