Triple
T12644232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montgomery Brewster |
E301978
|
entity |
| Predicate | timeConstraintOfInheritance |
P22110
|
FINISHED |
| Object | 30 days |
—
|
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: 30 days | Statement: [Montgomery Brewster, timeConstraintOfInheritance, 30 days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeConstraintOfInheritance Context triple: [Montgomery Brewster, timeConstraintOfInheritance, 30 days]
-
A.
timeLimited
chosen
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
B.
bindingTime
Indicates the point or period at which one entity becomes bound or committed to another, such as when a decision, value, or resource is fixed and no longer changeable.
-
C.
timeDefinite
Indicates that the associated event or state occurs at a clearly specified, fixed point or interval in time.
-
D.
durationDependsOn
Indicates that the length of time of one event or state is determined or influenced by another event, condition, or factor.
-
E.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
- 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_69d7bdec9f9c8190b4bac675b7588211 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ae493481908f82e0d05dce20bd |
completed | April 10, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69d960b47130819097e1162ed4fc993a |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:17 p.m.