Triple
T13812633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pro D2 |
E331930
|
entity |
| Predicate | tierInFrenchSystem |
P74340
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Pro D2, tierInFrenchSystem, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tierInFrenchSystem Context triple: [Pro D2, tierInFrenchSystem, 2]
-
A.
economicRankInFrance
Indicates the relative economic standing or ranking of an entity within the context of France’s economy.
-
B.
tierInNorthAmericanSystem
Indicates that an entity occupies a specified competitive or organizational level within the North American system for that domain (e.g., sports leagues, education, or other structured hierarchies).
-
C.
tierInDomesticSystem
chosen
Indicates the hierarchical level or rank that an entity occupies within a country's internal (domestic) system or structure.
-
D.
tierInBelgium
Indicates that an entity belongs to, is classified within, or operates at a specific tier or level in the context of Belgium.
-
E.
tierInLeagueSystem
Indicates the specific hierarchical level or division an entity occupies within an organized league system.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de027198f8819095da3e714ac241f5 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.