Triple
T7594666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Golden Jet |
E179826
|
entity |
| Predicate | personReferredToPosition |
P78055
|
FINISHED |
| Object | left wing |
—
|
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: left wing | Statement: [The Golden Jet, personReferredToPosition, left wing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personReferredToPosition Context triple: [The Golden Jet, personReferredToPosition, left wing]
-
A.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
B.
namedPersonOccupation
Indicates that a person is explicitly identified as having a particular occupation or job role.
-
C.
peakPersonnel
Indicates the maximum number of personnel involved or present at any point during a specified period or activity.
-
D.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
-
E.
namedForEmployer
Indicates that an entity is named after, or in honor of, its employer.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9bbcd8081909a229d7faa2ffdc8 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8184bb08190b2f70545a6aa277c |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:53 p.m.