Triple
T4384749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lindl. |
E99214
|
entity |
| Predicate | associatedWithCentury |
P56280
|
FINISHED |
| Object | 19th 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: 19th century | Statement: [Lindl., associatedWithCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCentury Context triple: [Lindl., associatedWithCentury, 19th century]
-
A.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
B.
acquiredInCentury
Indicates that one entity was acquired during a specific century represented by the other entity.
-
C.
declaredInCentury
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
D.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
-
E.
usedInCentury
Indicates that something (such as an object, practice, or concept) was in use during a specified century.
- 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_69b3454f739481909ff6c28331f0c0b9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35263970c8190904ee20d81715833 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f572efc8190bad1e5078cbcb75a |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:19 p.m.