Triple
T11434624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philipp |
E270972
|
entity |
| Predicate | associatedCenturyViaBearer |
P89519
|
FINISHED |
| Object | 18th 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: 18th century | Statement: [Philipp, associatedCenturyViaBearer, 18th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCenturyViaBearer Context triple: [Philipp, associatedCenturyViaBearer, 18th century]
-
A.
associatedWithCenturyOfNameBearer
chosen
Indicates that an entity is linked to the historical century in which the person (name bearer) associated with it lived or is primarily known.
-
B.
associatedWithCentury
Indicates that something has a relevant connection or linkage to a particular century, such as occurring in, belonging to, or being characteristic of that time period.
-
C.
hasNotableBearerCentury
Indicates that an entity has at least one notable bearer whose period of notability falls within the specified century.
-
D.
integrationCentury
Indicates the century during which an integration or unification process took place.
-
E.
namedAfterCentury
Indicates that something is named after a specific century, typically reflecting that century’s time period or characteristics.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d806c485f481909dd3d9b0993f3faf |
completed | April 9, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69d7e71436f88190ac7e45a04ea5c987 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.