Triple
T8143945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euclid's Elements |
E190161
|
entity |
| Predicate | wasStandardTextbookFor |
P27075
|
FINISHED |
| Object | geometry |
—
|
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: geometry | Statement: [Euclid's Elements, wasStandardTextbookFor, geometry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasStandardTextbookFor Context triple: [Euclid's Elements, wasStandardTextbookFor, geometry]
-
A.
notableTextbook
Indicates that a textbook is recognized as significant, influential, or widely used within its field or subject area.
-
B.
isStudiedUsing
Indicates that something serves as the method, tool, or approach by which something else is examined, analyzed, or researched.
-
C.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
D.
hasAcademicStandard
Indicates that an entity is associated with, aligned to, or governed by a specified academic or educational standard.
-
E.
becameStandardFor
chosen
Indicates that something was adopted and established as the usual or accepted norm for a particular purpose, context, or group.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4444bb248190beaaa2ce4b8f3eaa |
completed | March 31, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:36 p.m.