Triple
T8140047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simmons family |
E190071
|
entity |
| Predicate | typeOfNotability |
P74159
|
FINISHED |
| Object | regional historical notability |
—
|
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: regional historical notability | Statement: [Simmons family, typeOfNotability, regional historical notability]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfNotability Context triple: [Simmons family, typeOfNotability, regional historical notability]
-
A.
relativeNotability
Indicates how notable or prominent one entity is in comparison to another entity or set of entities.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
lacksNotabilityAs
Indicates that one entity is considered insufficiently notable or significant to be associated with or classified as the other entity.
-
D.
notableCategoryType
chosen
Indicates that an entity is notably associated with or classified under a particular category type.
-
E.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4404e5308190a323485701f09d86 |
completed | March 31, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:35 p.m.