Triple
T5474688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Callanish Stones |
E122919
|
entity |
| Predicate | hasApproximateNumberOfStones |
P19192
|
FINISHED |
| Object | about 13 stones in main circle |
—
|
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: about 13 stones in main circle | Statement: [Callanish Stones, hasApproximateNumberOfStones, about 13 stones in main circle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasApproximateNumberOfStones Context triple: [Callanish Stones, hasApproximateNumberOfStones, about 13 stones in main circle]
-
A.
numberOfStones
chosen
Indicates the quantitative count of stones associated with a given entity or context.
-
B.
hasApproximateNumberOfTombs
Indicates that an entity is associated with a tomb count that is approximate rather than exact.
-
C.
approximateNumberOfMoai
Indicates that one entity specifies an estimated or approximate count of Moai associated with another entity.
-
D.
hasNumberOfSquares
Indicates that an entity is associated with a specific count of squares it contains or comprises.
-
E.
hasApproximateNumberOfMiniatures
Indicates that an entity is associated with an estimated or non-exact count of miniatures.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9232ded08190b4142e604319b2ba |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.