Triple
T29586428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book I: General Norms |
E754034
|
entity |
| Predicate | endsWithCanon |
P20927
|
FINISHED |
| Object | canon 203 |
—
|
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: canon 203 | Statement: [Book I: General Norms, endsWithCanon, canon 203]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endsWithCanon Context triple: [Book I: General Norms, endsWithCanon, canon 203]
-
A.
endsWith
Indicates that one entity terminates with, or has as its final part, the sequence or element represented by the other entity.
-
B.
blendsWith
Indicates that one entity can be mixed or combined smoothly with another to form a uniform or harmonious result.
-
C.
endsUpWith
Indicates that, as a result of some process or sequence of events, one entity ultimately comes to possess, receive, or be associated with another entity.
-
D.
hasCapitalAtEnd
Indicates that the capital or uppercase letter appears at the end of the given string or sequence.
-
E.
hasEnding
chosen
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66d7dfb948190b35070cef785d6b8 |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:11 p.m.