Triple
T23889976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippe |
E600736
|
entity |
| Predicate | historicallyPopularInCentury |
P911
|
FINISHED |
| Object | 17th century |
—
|
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: 17th century | Statement: [Philippe, historicallyPopularInCentury, 17th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyPopularInCentury Context triple: [Philippe, historicallyPopularInCentury, 17th century]
-
A.
popularInCentury
chosen
Indicates that something was widely liked, influential, or commonly recognized during a specified century.
-
B.
historicallyPopularIn
Indicates that something was notably popular or widely favored within a particular place or context during a past historical period.
-
C.
notableFromCentury
Indicates that an entity is notably associated with, or best known from, a particular century.
-
D.
centuryCelebrated
Indicates that a particular century is being honored, commemorated, or formally celebrated in some way.
-
E.
celebratedSinceCentury
Indicates that a celebration, commemoration, or observance of something has been taking place continuously since a specified century.
- 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_69e295341ac0819080647f2908af793c |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cd029be48190b9319e59bf5d3a4d |
completed | April 29, 2026, 9:18 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:25 p.m.