Triple
T29404857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pidgin |
E745754
|
entity |
| Predicate | supportsProtocolType |
P35980
|
FINISHED |
| Object | multi-protocol |
—
|
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: multi-protocol | Statement: [Pidgin, supportsProtocolType, multi-protocol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProtocolType Context triple: [Pidgin, supportsProtocolType, multi-protocol]
-
A.
supportedProtocol
chosen
Indicates that one entity is compatible with, implements, or can operate using a specified communication or interaction protocol.
-
B.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
hasProtocol
Indicates that an entity uses, follows, or is governed by a specified protocol or set of procedural rules.
-
D.
supportsProgramType
Indicates that one entity is capable of handling, offering, or being compatible with a specified type of program.
-
E.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a036054129081909e66c5d62015e6c1 |
completed | May 12, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_6a035f17cbf88190acd6bdbfc9789ffb |
completed | May 12, 2026, 5:10 p.m. |
Created at: April 28, 2026, 2:53 p.m.