Triple
T2238125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lacringi |
E49328
|
entity |
| Predicate | historicalNotability |
P37289
|
FINISHED |
| Object | minor |
—
|
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: minor | Statement: [Lacringi, historicalNotability, minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalNotability Context triple: [Lacringi, historicalNotability, minor]
-
A.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
D.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
-
E.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
- F. None of above. chosen
Provenance (4 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_69a88aa84bdc819086df50e9c20b301e |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc096c7748190a545cc9b229bde62 |
completed | March 7, 2026, 6:07 a.m. |
| PD | Predicate disambiguation | batch_69abbdafc07881909101266a33ae7031 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf9c77fc8190a323bcaf644fb2c5 |
completed | March 7, 2026, 6:03 a.m. |
Created at: March 4, 2026, 7:47 p.m.