Triple
T13809428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eric Carlson |
E331845
|
entity |
| Predicate | hasMultiplePublicFigures |
P97477
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Eric Carlson, hasMultiplePublicFigures, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultiplePublicFigures Context triple: [Eric Carlson, hasMultiplePublicFigures, true]
-
A.
hasPublicFigureFounder
Indicates that an entity was founded by a person who is recognized as a public figure.
-
B.
hasNotablePersonAsFace
Indicates that an entity is publicly represented or symbolized by a specific notable person, such as a spokesperson, ambassador, or brand face.
-
C.
hasNotablePeople
chosen
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
-
D.
hasPublic
Indicates that an entity is accessible or visible to the general public rather than being private or restricted.
-
E.
hasNotablePersonConnection
Indicates that there exists a significant or noteworthy personal, professional, or historical relationship between the subject and the referenced person.
- 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_69d81c59f8808190a851bc56afdc55e9 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de026eae8481908b8880635e6a9152 |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc862e9608190bd8a3d883959b7e4 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:12 p.m.