Triple
T4603870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On First Principles |
E100382
|
entity |
| Predicate | textualHistory |
P44343
|
FINISHED |
| Object | original Greek largely lost |
—
|
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: original Greek largely lost | Statement: [On First Principles, textualHistory, original Greek largely lost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualHistory Context triple: [On First Principles, textualHistory, original Greek largely lost]
-
A.
historicalScript
Indicates that an entity is or was written in, or otherwise associated with, a particular historical writing system or script.
-
B.
historicalMedium
chosen
Indicates that an entity was conveyed, recorded, or expressed through a particular medium or format in its original historical context.
-
C.
writingMediumHistorical
Indicates that an entity historically used a particular medium or material as the means or surface for writing.
-
D.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
E.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
- 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_69bd43cce1e08190a07d53af6a9b6c24 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5975ec688190839bd22669343a76 |
completed | March 20, 2026, 2:28 p.m. |
| PD | Predicate disambiguation | batch_69bd522c811c81909aae4feadae33174 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:11 p.m.