Triple
T16391598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellenic F.C. |
E398064
|
entity |
| Predicate | RogerHuntStatus |
P123245
|
FINISHED |
| Object | legendary English striker |
—
|
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: legendary English striker | Statement: [Hellenic F.C., RogerHuntStatus, legendary English striker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RogerHuntStatus Context triple: [Hellenic F.C., RogerHuntStatus, legendary English striker]
-
A.
ChelseaCaptainStatus
Indicates the status or role of an entity as the captain of Chelsea Football Club.
-
B.
Joe Cole
Indicates a relationship or action involving the entity named "Joe Cole," such as participation, association, or attribution connected to him.
-
C.
RobOakeshottStatus
Indicates the specific political or public status associated with Rob Oakeshott in a given context or time.
-
D.
James Pearson
Indicates a relationship or action involving the entity named "James Pearson" and another entity, event, or attribute, depending on context.
-
E.
Jack Hively
Indicates a relationship or action involving the person named Jack Hively, such as authorship, direction, or participation in a work or event.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e326436ce881909f0f3899b8d931aa |
completed | April 18, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.