Triple
T17538749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Analytika protera |
E427127
|
entity |
| Predicate | hasCanonicalOrderWithinOrganon |
P127840
|
FINISHED |
| Object | third |
—
|
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: third | Statement: [Analytika protera, hasCanonicalOrderWithinOrganon, third]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCanonicalOrderWithinOrganon Context triple: [Analytika protera, hasCanonicalOrderWithinOrganon, third]
-
A.
hasCanonicalOrderInQuran
Indicates that there is a specific, officially recognized sequence or position of something within the canonical ordering of the Quran.
-
B.
isOrderOf
Indicates that one entity specifies the sequence, arrangement, or ranking in which elements of another entity are organized or occur.
-
C.
hasRankOrder
Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
-
D.
hasVerseOrder
Indicates that one verse is ordered or sequenced in relation to another verse within a structured text.
-
E.
isCanonicalFormOf
Indicates that one entity is the standard or officially accepted form or representation of another, often more variant, entity.
- F. None of above. chosen
Provenance (4 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4536ec5f48190acff6671712d40c7 |
completed | April 19, 2026, 4 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.