Triple
T21836441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostle of the Gauls |
E539131
|
entity |
| Predicate | recognizesStatusAs |
P59271
|
FINISHED |
| Object | leading missionary in Gaul |
—
|
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: leading missionary in Gaul | Statement: [Apostle of the Gauls, recognizesStatusAs, leading missionary in Gaul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recognizesStatusAs Context triple: [Apostle of the Gauls, recognizesStatusAs, leading missionary in Gaul]
-
A.
recognizesStatus
chosen
Indicates that one entity acknowledges or accepts the official status or standing of another entity.
-
B.
definedStatusFor
Indicates that one entity establishes or specifies the status or state assigned to another entity.
-
C.
isStatusOf
Indicates that a particular status or condition is assigned to, or characterizes, a specific entity.
-
D.
recognitionStatus
Indicates the current state or outcome of acknowledging, validating, or officially accepting something or someone.
-
E.
areRecognizedBy
Indicates that one entity acknowledges, identifies, or accepts another entity as valid, known, or legitimate.
- 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_69e0c475cda88190987d08f23caebdc1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0a7a7c368819094e0c4548be30798 |
completed | April 28, 2026, 12:27 p.m. |
| PD | Predicate disambiguation | batch_69e6be8c14748190bdcc44a14d50bea4 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:55 p.m.