Triple
T27561287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Background Intelligent Transfer Service |
E695773
|
entity |
| Predicate | startupType |
P177275
|
FINISHED |
| Object | Automatic (Delayed Start) |
—
|
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: Automatic (Delayed Start) | Statement: [Background Intelligent Transfer Service, startupType, Automatic (Delayed Start)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startupType Context triple: [Background Intelligent Transfer Service, startupType, Automatic (Delayed Start)]
-
A.
starterType
Indicates the classification or category of a starter (e.g., initial component, opening item, or first phase) associated with an entity or process.
-
B.
startingSystem
Indicates the system or context from which an action, process, or transition is initially begun.
-
C.
typicalStartType
chosen
Indicates the usual or most common type or category in which something begins or is initiated.
-
D.
launchServiceType
Indicates the type or category of launch service associated with an entity, such as the kind of launch operation or offering it provides.
-
E.
startupRole
Indicates that an entity holds a specific role or position within a startup organization.
- 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: April 27, 2026, 1:39 p.m.