Triple
T11239953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Corrigan |
E266044
|
entity |
| Predicate | typicalRoleType |
P85537
|
FINISHED |
| Object | quirky characters |
—
|
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: quirky characters | Statement: [Kevin Corrigan, typicalRoleType, quirky characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalRoleType Context triple: [Kevin Corrigan, typicalRoleType, quirky characters]
-
A.
typicalRole
Indicates that one entity serves as the usual, characteristic, or commonly expected role or function of another entity.
-
B.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
-
C.
typicalPerformerRoleType
chosen
Indicates the usual or characteristic role type that a performer commonly plays or is associated with in their performances.
-
D.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
E.
roleCharacteristic
Indicates that a particular characteristic, quality, or attribute is associated with and helps define a given role or function.
- 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e918375081908c2a7ccb50cbf331 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d7878906f48190b63ddc103a0c8f9b |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:30 p.m.