Triple
T37738203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On Providence (Panaetius, lost) |
E940634
|
entity |
| Predicate | inferredContentSource |
P22683
|
FINISHED |
| Object | later testimonia and doxographical reports |
—
|
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: later testimonia and doxographical reports | Statement: [On Providence (Panaetius, lost), inferredContentSource, later testimonia and doxographical reports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inferredContentSource Context triple: [On Providence (Panaetius, lost), inferredContentSource, later testimonia and doxographical reports]
-
A.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
-
B.
inferredType
Indicates that an entity has a type or category that has been deduced or derived rather than explicitly stated.
-
C.
detectedSourceType
Indicates the type or category of source from which something was detected.
-
D.
hasContentFrom
chosen
Indicates that one entity’s content is derived from, includes, or is based on another entity.
-
E.
usesSourceType
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
- 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_69f76ee0e32c8190b40a3b4cf590337c |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.