Triple
T11055041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pollard v. Hagan |
E261351
|
entity |
| Predicate | centuryDecided |
P47132
|
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: [Pollard v. Hagan, centuryDecided, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centuryDecided Context triple: [Pollard v. Hagan, centuryDecided, 19th century]
-
A.
century
Indicates that an entity is associated with, occurs in, or belongs to a particular 100-year time period.
-
B.
originalCentury
Indicates the century in which something was originally created, produced, or came into existence.
-
C.
lostCentury
Indicates that a particular century or era has been forgotten, obscured, or is missing from records or collective knowledge.
-
D.
declaredInCentury
chosen
Indicates that something (such as an event, work, or concept) was formally declared or proclaimed during a specified century.
-
E.
ruledUntilCentury
Indicates that a ruling relationship held by an entity continued in effect up to (but not necessarily including) 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d798a0890481909c1d4f9d5b23f33a |
completed | April 9, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69d7440da46c8190a77380d5d747ac9c |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.