Triple
T29094829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soddy circle |
E734966
|
entity |
| Predicate | hasMeasure |
P10736
|
FINISHED |
| Object | radius |
—
|
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: radius | Statement: [Soddy circle, hasMeasure, radius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeasure Context triple: [Soddy circle, hasMeasure, radius]
-
A.
hasMeasurement
chosen
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
B.
containsMeasure
Indicates that one entity includes or encompasses a specific measure or quantitative component as part of its content or structure.
-
C.
measureOf
Indicates that one entity serves as a quantitative or qualitative assessment or metric describing a property, extent, or magnitude of another entity.
-
D.
includesMeasure
Indicates that one entity contains, incorporates, or makes use of a particular measurement or quantitative value as part of its definition or specification.
-
E.
hasMeasurementRole
Indicates that an entity participates in a measurement activity in a specific functional role (e.g., as the measurer, instrument, or measured subject).
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 28, 2026, 11:07 a.m.