Triple
T17831460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olaus Petri |
E445266
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Petri |
—
|
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: Petri | Statement: [Olaus Petri, familyName, Petri]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petri Context triple: [Olaus Petri, familyName, Petri]
-
A.
Petri
chosen
Petri is a surname of German origin borne by various notable individuals across fields such as music, science, and the arts.
-
B.
Petry
Petry is a surname most notably associated with Ann Petry, an influential American novelist and short story writer known for exploring African American life and social issues.
-
C.
Piipaash
Piipaash are a Native American people of the lower Colorado River region, closely related to the Maricopa and known for their distinct language and cultural traditions.
-
D.
Petelia
Petelia was an ancient city in southern Italy that served as the principal center of the Bruttian people.
-
E.
Petosega
Petosega is a family name most notably associated with Chief Ignatius Petosega, a historical Indigenous leader.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48d248ecc8190b3f0d001b539d960 |
completed | April 19, 2026, 8:07 a.m. |
Created at: April 10, 2026, 10:15 a.m.