Triple
T16925024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King’s Men stone circle |
E410548
|
entity |
| Predicate | numberOfStonesOriginalEstimate |
P19192
|
FINISHED |
| Object | about 105 |
—
|
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 105 | Statement: [King’s Men stone circle, numberOfStonesOriginalEstimate, about 105]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfStonesOriginalEstimate Context triple: [King’s Men stone circle, numberOfStonesOriginalEstimate, about 105]
-
A.
numberOfStones
chosen
Indicates the quantitative count of stones associated with a given entity or context.
-
B.
usesOriginalStones
Indicates that something is constructed or preserved using the same stones that were part of the original structure or artifact.
-
C.
mineCountApproximate
Indicates that the number of mines associated with an entity is estimated or roughly counted rather than known exactly.
-
D.
approximateNumberOfMoai
Indicates that one entity specifies an estimated or approximate count of Moai associated with another entity.
-
E.
numberOfStoneHorses
Indicates the quantity of stone horses associated with a given subject or location.
- 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_69d886c7b1e481908c3766dfa8c13458 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cdf1347c819085cf754a0c3e19ed |
completed | April 18, 2026, 6:31 p.m. |
| PD | Predicate disambiguation | batch_69e32b982f548190b08414d55810de19 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:30 a.m.