Triple
T35218125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HOSR |
E1016871
|
entity |
| Predicate | usesTiming |
P67082
|
FINISHED |
| Object | staggered starts |
—
|
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: staggered starts | Statement: [HOSR, usesTiming, staggered starts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTiming Context triple: [HOSR, usesTiming, staggered starts]
-
A.
requiresTiming
Indicates that one entity’s occurrence, execution, or validity depends on being coordinated with a specific time or temporal condition related to another entity.
-
B.
usesTimingRules
chosen
Indicates that one entity applies or operates according to specified timing rules or constraints in relation to another entity or process.
-
C.
executionTiming
Indicates the temporal characteristics or schedule of when an action, process, or event is carried out.
-
D.
hasTimingCapability
Indicates that an entity possesses the ability to measure, control, or manage timing-related aspects of an operation or process.
-
E.
usesInterval
Indicates that one entity operates, functions, or is defined within a specific time or value interval associated with another entity.
- 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_69f76de072908190ab65038a8a7b6a79 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 3, 2026, 4:02 p.m.