Triple
T14896362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Metz |
E359885
|
entity |
| Predicate | hasYouthDevelopmentReputation |
P27334
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [FC Metz, hasYouthDevelopmentReputation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYouthDevelopmentReputation Context triple: [FC Metz, hasYouthDevelopmentReputation, yes]
-
A.
youthAcademyReputation
chosen
Indicates the perceived quality and success of an organization’s youth development system in producing and nurturing young talent.
-
B.
hasYouthTeam
Indicates that an entity has an associated youth team that serves as its junior or developmental squad.
-
C.
hasJuniorDevelopmentFocus
Indicates that an entity is oriented toward or primarily concerned with junior-level development activities or responsibilities.
-
D.
haveReputation
Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
-
E.
playedForJuniorTeam
Indicates that an individual was a member of and played for a specific junior-level sports team.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded6070b248190be8f4f91a0c0b1f3 |
completed | April 15, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69de9a4a14a88190951bb8f4c60bd37b |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:10 a.m.