Triple
T7361717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Burgoyne |
E169764
|
entity |
| Predicate | socialReputation |
P49959
|
FINISHED |
| Object | dashing personality |
—
|
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: dashing personality | Statement: [John Burgoyne, socialReputation, dashing personality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialReputation Context triple: [John Burgoyne, socialReputation, dashing personality]
-
A.
socialStance
Indicates the attitude, position, or orientation one entity holds toward another in a social context.
-
B.
crowdReputation
chosen
Indicates the collective opinion or perceived standing of an entity as judged by a group or general audience.
-
C.
socialSphere
Indicates the social environment or network within which an entity regularly interacts or maintains relationships.
-
D.
socialPosition
Indicates the relative social status, rank, or standing one entity holds within a social hierarchy or structure in relation to others.
-
E.
socialConnotation
Indicates the commonly understood social meaning, implication, or value judgment that people associate with something within a given cultural or social context.
- 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_69c68a59f2288190877ca15c19b1e822 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:06 p.m.