Triple
T10158475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAP |
E233828
|
entity |
| Predicate | relativeResourceUsage |
P45438
|
FINISHED |
| Object | heavier than LDAP |
—
|
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: heavier than LDAP | Statement: [DAP, relativeResourceUsage, heavier than LDAP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeResourceUsage Context triple: [DAP, relativeResourceUsage, heavier than LDAP]
-
A.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
-
B.
usesResourceSeparation
Indicates that one entity applies or enforces a separation of resources between entities or processes, preventing them from sharing or interfering with each other’s resources.
-
C.
runtimeApprox
Indicates an approximate or estimated duration of time that something (such as a process, program, or event) takes to run or complete.
-
D.
spaceUsage
chosen
Indicates how much physical or storage space is occupied or utilized by an entity relative to the total available space.
-
E.
resourceDepletionStatus
Indicates the current state or level of exhaustion of a particular resource, such as whether it is abundant, diminishing, or depleted.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba795808190acc9124c98c6e40f |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:09 p.m.