Triple
T29721727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M. 55 |
E752070
|
entity |
| Predicate | appliesToWorkCompletedInCentury |
P20496
|
FINISHED |
| Object | 20th 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: 20th century | Statement: [M. 55, appliesToWorkCompletedInCentury, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesToWorkCompletedInCentury Context triple: [M. 55, appliesToWorkCompletedInCentury, 20th century]
-
A.
completedInCentury
Indicates that an action, event, or creation was finished during a specified century.
-
B.
centuryOfWork
chosen
Indicates the century during which a particular work, activity, or contribution primarily took place.
-
C.
isSetInWorkPublishedInCentury
Indicates that the setting of a work takes place in another work that was published in a specified century.
-
D.
implementedInCentury
Indicates that an entity (such as a work, system, or concept) was created, developed, or put into effect during a specified century.
-
E.
ownedInCentury
Indicates that one entity owned another 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 28, 2026, 7:36 p.m.