Triple
T25672557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perfect Man |
E643716
|
entity |
| Predicate | furtherSystematizedInCentury |
P21503
|
FINISHED |
| Object | 14th 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: 14th century | Statement: [Perfect Man, furtherSystematizedInCentury, 14th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: furtherSystematizedInCentury Context triple: [Perfect Man, furtherSystematizedInCentury, 14th century]
-
A.
developedFurtherInCentury
chosen
Indicates that something was expanded, advanced, or more fully developed during the specified century.
-
B.
historicalPeriodOfSystematization
Indicates the historical period during which a practice, knowledge domain, or system was formally organized, codified, or systematized.
-
C.
formalizedInCentury
Indicates the century during which something was formally established, codified, or given official recognition.
-
D.
reorganizedInCentury
Indicates that an entity underwent a significant reorganization or structural change during the specified century.
-
E.
historicalFormulationCentury
Indicates the century during which something was originally formulated or first established.
- 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_69e77e7f69808190ad27df1006f6037a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fb3389ac819092997022ed2bc2f8 |
completed | May 2, 2026, 1:25 p.m. |
| PD | Predicate disambiguation | batch_69f4807f8680819098a524158d049c63 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 7:30 p.m.