Triple
T2523240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Valencia CF Mestalla |
E55572
|
entity |
| Predicate | playerAgeProfile |
P13613
|
FINISHED |
| Object | primarily under-23 players |
—
|
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: primarily under-23 players | Statement: [Valencia CF Mestalla, playerAgeProfile, primarily under-23 players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerAgeProfile Context triple: [Valencia CF Mestalla, playerAgeProfile, primarily under-23 players]
-
A.
featuredPlayerAge
Indicates the age of the player who is designated as the featured or highlighted participant in a given context.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
typicalPlayerProfile
chosen
Indicates the usual or characteristic attributes, behaviors, or demographics associated with a representative player in a given context.
-
D.
portraysAgeGroup
Indicates that one entity depicts or represents another entity as belonging to a particular age group.
-
E.
ageGroupRole
Indicates the role or function an entity has within a specific age group classification.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23a0a548190b44393e0f823f7a9 |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.