Triple
T21081292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foel Drygarn |
E519374
|
entity |
| Predicate | hasApproximateNumberOfCairns |
P142763
|
FINISHED |
| Object | over 200 |
—
|
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: over 200 | Statement: [Foel Drygarn, hasApproximateNumberOfCairns, over 200]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfCairns Context triple: [Foel Drygarn, hasApproximateNumberOfCairns, over 200]
-
A.
hasApproximateNumberOfCaves
Indicates that an entity is associated with an estimated or non-exact number of caves.
-
B.
hasApproximateNumberOfHills
Indicates that an entity is associated with an estimated or imprecise count of hills rather than an exact number.
-
C.
hasSummitCountApprox
Indicates that an entity is associated with an approximate number of summits or peak ascents.
-
D.
hasStaircaseToSummit
Indicates that there exists a staircase providing a direct route or access from a lower point to the summit of something.
-
E.
numberOfIndividualGeoglyphsApprox
Indicates an approximate count of distinct individual geoglyphs associated with a given subject.
- 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_69e0b506e59c8190849b71ed07929215 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e702db430c81908a1547d8fbe45506 |
completed | April 21, 2026, 4:53 a.m. |
| PD | Predicate disambiguation | batch_69e5dbfcd5e881908f1e4e0d2d237856 |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2e03d88819086f8b641656ad8b0 |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:49 p.m.