Triple
T4759906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeta |
E105673
|
entity |
| Predicate | alphabetOrderRelation |
P37518
|
FINISHED |
| Object | Epsilon < Zeta < Eta |
—
|
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: Epsilon < Zeta < Eta | Statement: [Zeta, alphabetOrderRelation, Epsilon < Zeta < Eta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alphabetOrderRelation Context triple: [Zeta, alphabetOrderRelation, Epsilon < Zeta < Eta]
-
A.
alphabet
Indicates that one entity is an alphabet or set of symbols used for representing elements (such as characters or tokens) in relation to another entity.
-
B.
letterSequence
Indicates that one sequence of letters directly follows or is ordered in relation to another within a larger string or alphabetic arrangement.
-
C.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
D.
alphabetType
Indicates the type or classification of an alphabet used by a writing system or language.
-
E.
hasNameOrder
Indicates the specific sequence or arrangement in which the components of a name (e.g., given name, family name, titles) are ordered.
- 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.