Triple
T13052859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabot |
E327489
|
entity |
| Predicate | isHistoricallyNotableFor |
P37289
|
FINISHED |
| Object | Age of Discovery exploration |
—
|
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: Age of Discovery exploration | Statement: [Cabot, isHistoricallyNotableFor, Age of Discovery exploration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isHistoricallyNotableFor Context triple: [Cabot, isHistoricallyNotableFor, Age of Discovery exploration]
-
A.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
B.
historicalNotability
chosen
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
sonNotableFor
Indicates that a son is recognized or distinguished for a particular achievement, role, or characteristic.
-
E.
notableAsNamesakeOf
Indicates that one entity is recognized or distinguished specifically for being the namesake of another entity.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:58 p.m.