Triple
T23155142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scrum |
E578417
|
entity |
| Predicate | definesTimebox |
P38735
|
FINISHED |
| Object | Daily Scrum is 15 minutes or less |
—
|
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: Daily Scrum is 15 minutes or less | Statement: [Scrum, definesTimebox, Daily Scrum is 15 minutes or less]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesTimebox Context triple: [Scrum, definesTimebox, Daily Scrum is 15 minutes or less]
-
A.
timeLimited
Indicates that the relationship or action is constrained to occur or remain valid only within a specific, limited time period.
-
B.
regulatesTimeFor
Indicates that one entity controls, influences, or sets the timing or schedule of another entity’s activities or processes.
-
C.
timeDefinite
Indicates that the associated event or state occurs at a clearly specified, fixed point or interval in time.
-
D.
timeFrameSpecified
chosen
Indicates that a specific temporal period or duration has been explicitly defined or constrained for the related event, action, or relationship.
-
E.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
- 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_69e245fb8de081908f0eba7b5fd75bc4 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18efca1f081908ff1c34ba25f40c3 |
completed | April 29, 2026, 4:54 a.m. |
| PD | Predicate disambiguation | batch_69ef89ff76808190808ee4ad9dea776b |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:01 p.m.