Triple
T4308023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Name Is Aram |
E94002
|
entity |
| Predicate | isSetInTimePeriod |
P56370
|
FINISHED |
| Object | early 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: early 20th century | Statement: [My Name Is Aram, isSetInTimePeriod, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSetInTimePeriod Context triple: [My Name Is Aram, isSetInTimePeriod, early 20th century]
-
A.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
B.
inForceInPeriod
Indicates that something (such as a rule, contract, or condition) is valid, applicable, or legally effective during a specified time period.
-
C.
hasCollectionFromPeriod
Indicates that a collection originates from, or is associated with, a specific historical or temporal period.
-
D.
hasInceptionPeriod
Indicates the time span or period during which something begins or comes into existence.
-
E.
hasCountingPeriod
Indicates that there is a defined time span or interval over which occurrences, quantities, or measurements related to an entity are counted or aggregated.
- 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_69b3451886588190a3dd1305ea7c58dc |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b350d2af088190ad7cb035d6e0f8c2 |
completed | March 12, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69b34f4a07b08190a06ada0d9cbb14fb |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:11 p.m.