Triple
T27755844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .NET Remoting |
E701330
|
entity |
| Predicate | supportsActivationMode |
P99857
|
FINISHED |
| Object | server-activated objects |
—
|
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: server-activated objects | Statement: [.NET Remoting, supportsActivationMode, server-activated objects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsActivationMode Context triple: [.NET Remoting, supportsActivationMode, server-activated objects]
-
A.
canBeActivatedFor
Indicates that one entity is capable of being put into an active or operational state by or for another entity.
-
B.
supportedMode
chosen
Indicates that a system, device, or component is capable of operating in or handling a particular mode.
-
C.
canBeActivatedWithin
Indicates that one entity is capable of being activated or triggered within the spatial or temporal bounds defined by another entity.
-
D.
activationType
Indicates the specific manner or mechanism by which an activation or triggering event occurs between entities.
-
E.
supportsActivity
Indicates that one entity provides the necessary conditions, resources, or environment for another entity’s activity to occur or be sustained.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a00037bf4148190a58593d30efdd3f8 |
completed | May 10, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_6a0000b7af608190b718fc4111bcdad8 |
completed | May 10, 2026, 3:51 a.m. |
Created at: April 27, 2026, 4:23 p.m.