Triple
T15670633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Doyenne |
E377300
|
entity |
| Predicate | notableFeatureOfRace |
P118447
|
FINISHED |
| Object | hilly Ardennes terrain |
—
|
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: hilly Ardennes terrain | Statement: [La Doyenne, notableFeatureOfRace, hilly Ardennes terrain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFeatureOfRace Context triple: [La Doyenne, notableFeatureOfRace, hilly Ardennes terrain]
-
A.
notableRaceCharacteristic
chosen
Indicates that an entity is distinguished by a particular race-related trait or attribute that is especially prominent or noteworthy.
-
B.
notableFeatureOn
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
C.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
D.
hasNotableRace
Indicates that an entity is associated with a race or competition that is considered notable or significant.
-
E.
relatedRace
Indicates that there is a connection or association between two races, such as similarity, relevance, or contextual linkage.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f1254508190a77a16b7bfd299ad |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8b36a4819081cb5708fe77ef51 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:16 a.m.