Triple
T33910295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caesar and Christ |
E869293
|
entity |
| Predicate | hasVolumeInSeriesBefore |
P179400
|
FINISHED |
| Object | Our Oriental Heritage |
—
|
NE NERFINISHED |
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: Our Oriental Heritage | Statement: [Caesar and Christ, hasVolumeInSeriesBefore, Our Oriental Heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVolumeInSeriesBefore Context triple: [Caesar and Christ, hasVolumeInSeriesBefore, Our Oriental Heritage]
-
A.
precedesInVolume
Indicates that one entity appears earlier than another in the ordered sequence of items within the same volume.
-
B.
inSeriesBefore
chosen
Indicates that one item appears earlier than another in an ordered series or sequence.
-
C.
isBoundVolumeSeries
Indicates that one entity is a series composed of multiple bound volumes that are physically or conceptually grouped together.
-
D.
hasSeriesRecord
Indicates that one entity maintains a documented record or history of another entity’s participation or performance within a series.
-
E.
followsInVolume
Indicates that one entity appears or occurs later than another within the ordered sequence of a volume (such as a book, journal, or series).
- 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_69f3499869bc8190b6c33a81686af226 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: May 1, 2026, 1:48 a.m.