Triple
T4759903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeta |
E105673
|
entity |
| Predicate | usedInNumberSystem |
P6517
|
FINISHED |
| Object | Greek numerals |
—
|
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: Greek numerals | Statement: [Zeta, usedInNumberSystem, Greek numerals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInNumberSystem Context triple: [Zeta, usedInNumberSystem, Greek numerals]
-
A.
hasNumberSystem
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
B.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
C.
notableNumber
Indicates that a number associated with an entity is distinguished or significant in some notable way (e.g., record-setting, symbolic, or otherwise remarkable).
-
D.
notationSystem
chosen
Indicates a relationship where one entity is the system or method of notation used to represent or encode another entity.
-
E.
logarithmBaseDetermines
Indicates that the chosen base of a logarithm determines how a quantity is expressed or scaled in logarithmic terms.
- 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_69bd43f14cac819081c7c69803648211 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd650dc7fc81909b483ef3c456ae0d |
completed | March 20, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69bd6225c9488190afee5bb3619d0365 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:20 p.m.