Triple
T35300716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arsenal F.C. youth teams |
E1019495
|
entity |
| Predicate | secondaryYouthSide |
P199533
|
FINISHED |
| Object | Arsenal Under-18s |
—
|
NE NERFINISHED |
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: Arsenal Under-18s | Statement: [Arsenal F.C. youth teams, secondaryYouthSide, Arsenal Under-18s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryYouthSide Context triple: [Arsenal F.C. youth teams, secondaryYouthSide, Arsenal Under-18s]
-
A.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
B.
secondaryOpponent
Indicates that an entity serves as an additional or backup opponent to a primary one in a given context or interaction.
-
C.
secondaryTheater
Indicates that an entity serves as a secondary or supporting theater or venue in relation to a primary one.
-
D.
secondaryBoard
Indicates that one entity serves as a secondary or auxiliary board associated with another primary entity.
-
E.
secondarySee
Indicates that one entity is referenced as an additional or alternative point of consultation or viewing in relation to another entity.
- 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_69f76de7eedc8190a3bdc64ebbc05b42 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
| PDg | Predicate description generation | batch_69ff409ee6ec819088b7c13fabed2ac2 |
completed | May 9, 2026, 2:11 p.m. |
Created at: May 3, 2026, 4:03 p.m.