Triple
T25209412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | (Bong.) Carrière |
E631640
|
entity |
| Predicate | authorAbbreviationIncludes |
P33057
|
FINISHED |
| Object | Carrière |
—
|
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: Carrière | Statement: [(Bong.) Carrière, authorAbbreviationIncludes, Carrière]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorAbbreviationIncludes Context triple: [(Bong.) Carrière, authorAbbreviationIncludes, Carrière]
-
A.
authorAbbreviation
chosen
Indicates that one entity is the standardized abbreviated form of an author's name used in citations or references for another entity.
-
B.
authorType
Indicates the specific role or category of authorship associated with an entity, such as primary author, co-author, or editor.
-
C.
authorTitle
Indicates that a person is the creator or writer of a work that bears the specified title.
-
D.
workAuthorIs
Indicates that a specific person or entity is the author or creator of a particular work.
-
E.
authorOfNamesFor
Indicates that one entity is the creator or originator of the names assigned to another entity or set of entities.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1379f08190836c3e02b0c892df |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 21, 2026, 12:58 p.m.