Triple
T38659293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agapius |
E939984
|
entity |
| Predicate | placeInSources |
P184368
|
FINISHED |
| Object | Acts of Saint Eustace (legendary acts) |
—
|
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: Acts of Saint Eustace (legendary acts) | Statement: [Agapius, placeInSources, Acts of Saint Eustace (legendary acts)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeInSources Context triple: [Agapius, placeInSources, Acts of Saint Eustace (legendary acts)]
-
A.
usedInSources
chosen
Indicates that something is referenced, applied, or employed within one or more information sources.
-
B.
placeInSeries
Indicates the position or order that something occupies within a sequence or series.
-
C.
laterSources
Indicates that the information, claim, or reference is derived from sources that were created or recorded at a later time than the event or material being discussed.
-
D.
placementIn
Indicates that one entity is located or positioned within the spatial or structural bounds of another entity.
-
E.
sourcesInclude
Indicates that one entity’s content, data, or information is derived from, references, or incorporates material from another specified source.
- 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_69f76ede49648190a48bfe47032a05a3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: May 3, 2026, 4:33 p.m.