Triple
T32141476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navarro–Frenk–White profile |
E820913
|
entity |
| Predicate | centralSlope |
P192069
|
FINISHED |
| Object | −1 |
—
|
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: −1 | Statement: [Navarro–Frenk–White profile, centralSlope, −1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralSlope Context triple: [Navarro–Frenk–White profile, centralSlope, −1]
-
A.
centralPeak
Indicates that one entity is the central, elevated peak located near the middle of another entity, typically within a larger structure such as a crater or basin.
-
B.
usesIntermediateSlope
Indicates that an entity employs or operates on a slope of intermediate steepness as part of its process or behavior.
-
C.
centralIn
Indicates that one entity occupies a central or most important position within another entity, context, or structure.
-
D.
centerIs
Indicates that one entity serves as the central point or middle position of another entity or space.
-
E.
centralLine
Indicates that one entity serves as the primary or central reference line relative to another entity or within a given structure.
- F. None of above. chosen
Provenance (4 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_69f3490520d081909b2f1271dab75faa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: May 1, 2026, 12:30 a.m.