Triple
T34823334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA U-17 World Cup 1999 |
E1003847
|
entity |
| Predicate | teamQuotaPerSquad |
P3315
|
FINISHED |
| Object | 18 |
—
|
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: 18 | Statement: [FIFA U-17 World Cup 1999, teamQuotaPerSquad, 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: teamQuotaPerSquad Context triple: [FIFA U-17 World Cup 1999, teamQuotaPerSquad, 18]
-
A.
squadRestrictionForInvitedTeams
Indicates a constraint or rule that applies to the squad composition or size specifically for teams that have been invited.
-
B.
teamConstraint
Indicates a rule or limitation governing how entities can be grouped, associated, or operate together as a team.
-
C.
teamRosterLimit
chosen
Indicates the maximum number of members that are allowed to be on a team’s roster.
-
D.
teamLimitPerGame
Indicates the maximum number of times a team is allowed to participate or be involved in a single game or match.
-
E.
teamLimitPerAssociation
Indicates the maximum number of teams that can be associated with a single association or grouping.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77adf71d88190812e930bcf1e2ce5 |
completed | May 3, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 4 p.m.