Triple
T32790190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Syncellus |
E838604
|
entity |
| Predicate | chronologySystemUsed |
P88531
|
FINISHED |
| Object | biblical chronology |
—
|
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: biblical chronology | Statement: [George Syncellus, chronologySystemUsed, biblical chronology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologySystemUsed Context triple: [George Syncellus, chronologySystemUsed, biblical chronology]
-
A.
chronologyUsedBy
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
B.
chronologyType
chosen
Indicates the type or system of chronological ordering or dating applied to an event, period, or sequence.
-
C.
chronologyStyle
Indicates how events, actions, or states are ordered or structured in time relative to one another.
-
D.
chronologyNote
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
E.
chronologyEstablishedBy
Indicates that the temporal order or dating of events, objects, or periods is determined or defined by a specified source, method, or authority.
- 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_69f3493b83f48190be335cd42465cecf |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 1, 2026, 1:14 a.m.