Triple
T27755850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .NET Remoting |
E701330
|
entity |
| Predicate | supportsFormatter |
P203
|
FINISHED |
| Object | binary formatter |
—
|
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: binary formatter | Statement: [.NET Remoting, supportsFormatter, binary formatter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsFormatter Context triple: [.NET Remoting, supportsFormatter, binary formatter]
-
A.
supportsForm
Indicates that one entity provides compatibility or backing for a particular form, format, or type associated with another entity.
-
B.
supportsTextFormat
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified text format.
-
C.
supportsForms
Indicates that one entity is capable of handling, accepting, or working with specific forms or form types associated with another entity.
-
D.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
supportsAt
Indicates that one entity provides assistance, endorsement, or backing to another entity in a specific context, location, or point in time.
- 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_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: April 27, 2026, 4:23 p.m.