Triple
T37619655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | François |
E936028
|
entity |
| Predicate | hasHistoricalProminence |
P37289
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [François, hasHistoricalProminence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalProminence Context triple: [François, hasHistoricalProminence, yes]
-
A.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
B.
hasHistoricalRecognitionAs
Indicates that an entity is formally or widely acknowledged in a historical context as having a particular role, status, or identity.
-
C.
hasHistoricalSignificanceThrough
Indicates that one entity possesses historical importance or relevance by means of, or as established through, its connection or association with another entity or event.
-
D.
historicalNotability
chosen
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
E.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
- 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_69f76ed16b748190ad6add183b1be688 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9361943c81909544203cbc998a69 |
completed | May 9, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69ff913138a08190b59bdc9d8d199eb3 |
completed | May 9, 2026, 7:55 p.m. |
Created at: May 3, 2026, 4:18 p.m.