Triple
T28793370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manilius |
E727018
|
entity |
| Predicate | fieldOfDiscussion |
P165591
|
FINISHED |
| Object | political philosophy |
—
|
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: political philosophy | Statement: [Manilius, fieldOfDiscussion, political philosophy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfDiscussion Context triple: [Manilius, fieldOfDiscussion, political philosophy]
-
A.
topicOfDiscourse
chosen
Indicates that something serves as the subject or focus of a particular discussion, conversation, or communicative act.
-
B.
frequentlyDiscussedIn
Indicates that a topic, subject, or entity is often the focus of conversation, debate, or mention within a particular context or medium.
-
C.
fieldOfDebate
Indicates that something is the subject or domain around which a debate or argumentative discussion is centered.
-
D.
topicOfDialogue
Indicates that a particular subject or theme is the main focus of a dialogue or conversation between entities.
-
E.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
- 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_69f0319b7c44819085736bcc256185e6 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 28, 2026, 6:24 a.m.