Triple
T8678614
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada goose |
E205977
|
entity |
| Predicate | typicalFlightFormation |
P57566
|
FINISHED |
| Object | V-shaped formation |
—
|
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: V-shaped formation | Statement: [Canada goose, typicalFlightFormation, V-shaped formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFlightFormation Context triple: [Canada goose, typicalFlightFormation, V-shaped formation]
-
A.
notableAirFormation
Indicates a significant or noteworthy configuration, pattern, or structure formed in the air (such as clouds, smoke, or other aerial phenomena).
-
B.
formationFlying
chosen
Indicates that multiple entities are flying in a coordinated, organized pattern relative to one another.
-
C.
navalFormation
Indicates a relationship where multiple naval units are organized into a coordinated tactical or operational group.
-
D.
typicalFormation
Indicates the usual or characteristic way in which something is formed, structured, or comes into existence.
-
E.
tacticalFormation
Indicates a specific strategic arrangement or positioning of entities relative to one another to achieve a tactical objective.
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae6d19c8190be003f7901c0468d |
completed | March 31, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.