Triple
T1053347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boeing 747 |
E22746
|
entity |
| Predicate | typicalCrew |
P883
|
FINISHED |
| Object | 2 pilots |
—
|
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: 2 pilots | Statement: [Boeing 747, typicalCrew, 2 pilots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCrew Context triple: [Boeing 747, typicalCrew, 2 pilots]
-
A.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
-
B.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
C.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
D.
crewCountApproximate
chosen
Indicates that the relationship specifies an estimated or approximate number of crew members associated with an entity.
-
E.
hasCrewRole
Indicates that an entity serves in a specific role or position within a crew associated with another 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_69a493da02e081908c13ff5e02a0fe7a |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8b644088190a1f0f00f97941298 |
completed | March 1, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69a4b731e25c8190b5ea8466648c2c9a |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.