Triple
T207031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollodorus' Bibliotheca |
E4630
|
entity |
| Predicate | scholarlyDebate |
P3464
|
FINISHED |
| Object | authorship and exact dating |
—
|
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: authorship and exact dating | Statement: [Apollodorus' Bibliotheca, scholarlyDebate, authorship and exact dating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scholarlyDebate Context triple: [Apollodorus' Bibliotheca, scholarlyDebate, authorship and exact dating]
-
A.
scholarlyView
chosen
Indicates that one entity holds an academic or research-based interpretation, opinion, or theoretical stance about another entity.
-
B.
languageOfDebate
Indicates that a specified language is the one used for conducting a particular debate.
-
C.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
D.
debatedAt
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
-
E.
contestedBy
Indicates that one party challenges, disputes, or opposes a claim, decision, or position held by another party.
- 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_69a25737567c81908f9c505300239181 |
completed | Feb. 28, 2026, 2:47 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b4c7f908190876c1041db52dffc |
completed | Feb. 28, 2026, 3:04 a.m. |
Created at: Feb. 28, 2026, 2:51 a.m.