Triple
T898822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greek alphabet |
E19401
|
entity |
| Predicate | numericSystem |
P5213
|
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: [Greek alphabet, numericSystem, Greek numerals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numericSystem Context triple: [Greek alphabet, numericSystem, Greek numerals]
-
A.
hasNumberSystem
chosen
Indicates that an entity possesses or uses a particular system for representing and organizing numbers.
-
B.
notationSystem
Indicates a relationship where one entity is the system or method of notation used to represent or encode another entity.
-
C.
number
Indicates that one entity is associated with a specific numerical value or count in relation to another entity or context.
-
D.
denominationSystem
Indicates a relationship where one entity defines, uses, or belongs to a particular system of denominations (such as units, values, or classifications) established by another entity.
-
E.
numericCode
Indicates that an entity is associated with a specific numerical identifier or classification code.
- 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_69a4939e889c8190ac148b3ac1a7f90b |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad4162848190aa2787b2fa3e6575 |
completed | March 1, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69a4aa979d408190b17ccfde132ea628 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.