Triple
T13464227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London (during Arsenal career) |
E311453
|
entity |
| Predicate | eraOfAssociationEnd |
P64656
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [London (during Arsenal career), eraOfAssociationEnd, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraOfAssociationEnd Context triple: [London (during Arsenal career), eraOfAssociationEnd, 2002]
-
A.
elementalAssociation
Indicates an association where one entity is linked or related to a particular element or elemental property (such as fire, water, earth, or air).
-
B.
eraOfBoundaryRole
Indicates the historical period or era during which a particular boundary role is defined, active, or relevant.
-
C.
participatingAssociations
Indicates that certain associations are involved as participants in a given activity, event, or relationship.
-
D.
protégéOf
Indicates that one entity is mentored, trained, or guided in their development by another, more experienced entity.
-
E.
associatedWithAssociation
chosen
Indicates a relationship where an entity is linked or connected to a particular association or organization.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0f1830819085700b4521e44678 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69dbadfddefc81909ef7fde23b181b5c |
completed | April 12, 2026, 2:36 p.m. |
Created at: April 9, 2026, 9:41 p.m.