Triple
T703894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linfield FC |
E14057
|
entity |
| Predicate | recordHolderFor |
P2722
|
FINISHED |
| Object | most Irish League titles |
—
|
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: most Irish League titles | Statement: [Linfield FC, recordHolderFor, most Irish League titles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordHolderFor Context triple: [Linfield FC, recordHolderFor, most Irish League titles]
-
A.
recordHeldFrom
Indicates that a record or position was held by an entity starting from a specified point in time.
-
B.
recordHeld
chosen
Indicates that one entity possesses or maintains a particular record associated with another entity or context.
-
C.
notableHolder
Indicates that a person or entity is a distinguished or prominent holder of a particular position, title, or role.
-
D.
lastHolder
Indicates that the subject is the most recent entity to have possessed, owned, or held the object.
-
E.
originalHolder
Indicates that an entity is the initial possessor or owner of another entity before any transfer, change, or reassignment occurs.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58d4c3c8190ad4527d14bca5e6e |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4edc33881909a978268f6dd5d82 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.