Triple
T11411481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Coryell |
E270380
|
entity |
| Predicate | usesFormation |
P49857
|
FINISHED |
| Object | single-back sets |
—
|
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-back sets | Statement: [Air Coryell, usesFormation, single-back sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFormation Context triple: [Air Coryell, usesFormation, single-back sets]
-
A.
containsFormation
Indicates that one entity spatially or structurally includes or encloses a formation as part of its extent or composition.
-
B.
onFormation
Indicates that one entity is located on or attached to the surface of a formation (such as a geological or structural feature).
-
C.
associatedFormation
chosen
Indicates that one entity is linked or connected to a particular formation, such as a geological, structural, or organizational configuration.
-
D.
supportedFormation
Indicates that one entity provided assistance, resources, or conditions that enabled the creation or establishment of another entity or structure.
-
E.
usesForm
Indicates that one entity employs, applies, or operates through a particular form, format, or structured representation of something.
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8015017d08190b4020c76545556d6 |
completed | April 9, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.