Triple
T31248188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roda Island Nilometer complex |
E796746
|
entity |
| Predicate | hasMeasurementScale |
P3868
|
FINISHED |
| Object | cubit markings |
—
|
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: cubit markings | Statement: [Roda Island Nilometer complex, hasMeasurementScale, cubit markings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeasurementScale Context triple: [Roda Island Nilometer complex, hasMeasurementScale, cubit markings]
-
A.
hasScale
chosen
Indicates that one entity possesses or is characterized by a scale or graduated measurement system related to another entity.
-
B.
hasMeasurement
Indicates that an entity is associated with a specific measured value, often including a unit or measurement context.
-
C.
hasScales
Indicates that an entity possesses scales as a surface covering or body feature.
-
D.
hasMeasurementRole
Indicates that an entity participates in a measurement activity in a specific functional role (e.g., as the measurer, instrument, or measured subject).
-
E.
containsMeasure
Indicates that one entity includes or encompasses a specific measure or quantitative component as part of its content or structure.
- 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_69f224dc84d0819081f1cb6f9127e6b1 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fe031bc6208190860099aef72d8dcb |
completed | May 8, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69fe014c8b388190b5d4e0cb95ee2be5 |
completed | May 8, 2026, 3:29 p.m. |
Created at: April 29, 2026, 9:11 p.m.