Triple
T35797488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Restoration-era Paris |
E1034872
|
entity |
| Predicate | notableIntellectualActiveIn |
P206051
|
FINISHED |
| Object | Benjamin Constant |
E227209
|
NE 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: Benjamin Constant | Statement: [Restoration-era Paris, notableIntellectualActiveIn, Benjamin Constant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableIntellectualActiveIn Context triple: [Restoration-era Paris, notableIntellectualActiveIn, Benjamin Constant]
-
A.
notableHuman
Indicates that the subject is a human who is recognized as notable or significant in some context.
-
B.
notableIndividuals
Indicates that certain individuals are recognized as particularly important, famous, or influential in relation to something.
-
C.
notableCulturalFigure
Indicates that a person holds significant influence or recognition within a culture’s arts, traditions, values, or public life.
-
D.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
-
E.
notableAchiever
Indicates that an entity has achieved notable success, distinction, or recognition in a particular field or domain.
- F. None of above. chosen
Provenance (5 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_69f76e169bd081909f16cd8c9ee7870c |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38a4d935988190b0e265c841c29ecf |
completed | June 22, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037ce53de881908cf14141cf3bc570 |
completed | May 12, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:06 p.m.