Triple
T10466683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alphabetical Order |
E246813
|
entity |
| Predicate | isWrittenInProse |
P6480
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Alphabetical Order, isWrittenInProse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWrittenInProse Context triple: [Alphabetical Order, isWrittenInProse, yes]
-
A.
hasProseDialogue
Indicates that one entity contains or features spoken or conversational content expressed in prose form involving another entity.
-
B.
hasProseAndVerse
Indicates that something contains both prose and verse forms within it.
-
C.
hasFictionComponent
Indicates that something includes, contains, or is composed in part of a fictional element or work.
-
D.
currentlyWrittenIn
Indicates that a work or document is, at the present time, expressed or composed in a particular language or writing system.
-
E.
hasLiteraryForm
chosen
Indicates that one entity is expressed, structured, or realized in a particular literary form (such as a genre, style, or textual format).
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5092d6d408190b6bda4d7ced4601e |
completed | April 7, 2026, 1:39 p.m. |
| PD | Predicate disambiguation | batch_69d4fb84bafc8190819757b93620508a |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:19 p.m.