Triple
T27471380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adelaide Brooke |
E693327
|
entity |
| Predicate | fixedPointInTime |
P54535
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Adelaide Brooke, fixedPointInTime, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fixedPointInTime Context triple: [Adelaide Brooke, fixedPointInTime, yes]
-
A.
timeDefinite
chosen
Indicates that the associated event or state occurs at a clearly specified, fixed point or interval in time.
-
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.
fixedTerm
Indicates that the relationship, agreement, or condition applies for a predetermined, non-variable duration of time.
-
D.
timingOfPoints
Indicates the temporal relationship or sequence in which the points or events occur.
-
E.
timeIndexed
Indicates that the relationship or property it connects is associated with, or valid during, a specific time or time interval.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f62e01958c8190925c7f71b0ba0150 |
completed | May 2, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:54 p.m.