Triple
T13019836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TQuery |
E322643
|
entity |
| Predicate | lifecycleManagedBy |
P107490
|
FINISHED |
| Object | Delphi form designer |
—
|
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: Delphi form designer | Statement: [TQuery, lifecycleManagedBy, Delphi form designer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifecycleManagedBy Context triple: [TQuery, lifecycleManagedBy, Delphi form designer]
-
A.
lifecycleTiedTo
Indicates that the existence, duration, or validity of one entity is dependent on and ends with the lifecycle of another entity.
-
B.
lifecycleType
Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
-
C.
lifecycleModel
Indicates that one entity defines or follows the structured sequence of phases or stages governing the development, use, and retirement of another entity.
-
D.
laterManagedBy
Indicates that an entity was, at a subsequent time, managed or overseen by another entity.
-
E.
isManagedThrough
Indicates that one entity is administered, controlled, or operated by means of another entity, typically specifying the mechanism, channel, or system used for its management.
- F. None of above. chosen
Provenance (4 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97ecf21bc819082fb512bc479b4be |
completed | April 10, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
| PDg | Predicate description generation | batch_69d97e3df2288190a7f27d31d248bb7f |
completed | April 10, 2026, 10:48 p.m. |
Created at: April 9, 2026, 8:51 p.m.