Triple
T25313410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orgetorix |
E634665
|
entity |
| Predicate | primarySourceBias |
P180917
|
FINISHED |
| Object | Roman perspective |
—
|
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: Roman perspective | Statement: [Orgetorix, primarySourceBias, Roman perspective]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primarySourceBias Context triple: [Orgetorix, primarySourceBias, Roman perspective]
-
A.
primarySources
Indicates that one entity serves as an original, authoritative source of information or evidence for another entity.
-
B.
primarySourcesDiscussed
Indicates that the primary source materials are examined, analyzed, or discussed in relation to the subject.
-
C.
primaryContentOrigin
Indicates that one entity is the main or original source from which the content of another entity is derived.
-
D.
editorialSource
Indicates that one entity serves as the editorial origin, provider, or authority for the content or information associated with another entity.
-
E.
primarySourceArea
Indicates that something originates from, or is chiefly derived from, a specified source area.
- F. None of above. chosen
Provenance (4 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_69e75a9847c08190bb02990d06d5ffb7 |
completed | April 21, 2026, 11:08 a.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. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 21, 2026, 1:27 p.m.