Triple
T27582602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DeltaV |
E699619
|
entity |
| Predicate | definesResourceType |
P56536
|
FINISHED |
| Object | version-controlled resource |
—
|
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: version-controlled resource | Statement: [DeltaV, definesResourceType, version-controlled resource]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesResourceType Context triple: [DeltaV, definesResourceType, version-controlled resource]
-
A.
definesType
chosen
Indicates that one entity specifies or establishes the type or classification of another entity.
-
B.
contributingResourceType
Indicates the type or category of a resource that contributes to or supports another resource or activity.
-
C.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
D.
hasTypeOfResource
Indicates that an entity is associated with a specific category or kind of resource it represents or utilizes.
-
E.
managesResourceType
Indicates that an entity is responsible for overseeing, controlling, or administering a particular type or category of resource.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 27, 2026, 2:03 p.m.