Triple
T15011285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Born family |
E377840
|
entity |
| Predicate | hasMemberActiveInCentury |
P1560
|
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: [Born family, hasMemberActiveInCentury, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberActiveInCentury Context triple: [Born family, hasMemberActiveInCentury, 19th century]
-
A.
activeInCentury
chosen
Indicates that an entity was active, influential, or operational during a specified century.
-
B.
hasAncientMember
Indicates that at least one member of a group, set, or collection originates from or belongs to an ancient time period.
-
C.
existsSinceCentury
Indicates that an entity has existed or been in effect since a specified century.
-
D.
existedInCentury
Indicates that an entity existed or was present during a specified century.
-
E.
signedInCentury
Indicates that an entity (such as a document, treaty, or agreement) was signed during 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded734943481908dad4ceed4fe850c |
completed | April 15, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69de9a6531a88190acde65199a477350 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:55 a.m.