Triple
T8756323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protocol Buffers |
E208079
|
entity |
| Predicate | supportsTextFormat |
P85212
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Protocol Buffers, supportsTextFormat, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTextFormat Context triple: [Protocol Buffers, supportsTextFormat, true]
-
A.
supportsBackupFormat
Indicates that one entity is capable of handling, storing, or operating with another entity as a backup data format.
-
B.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
C.
supportsNarrativeText
Indicates that one entity provides justification, evidence, or contextual backing that helps explain or validate the narrative content expressed by another entity.
-
D.
supportsMarkdown
Indicates that one entity provides the ability for another entity to use or display content formatted in Markdown.
-
E.
usesTextService
Indicates that an entity makes use of a text-based service to perform some function or obtain some benefit.
- F. None of above. chosen
Provenance (4 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_69ca835cd6b08190bd7c63db92f53c86 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5dd95e9481909cc88e8d91601754 |
completed | March 31, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69cc5c160dac8190b4aeb4bf0529de52 |
completed | March 31, 2026, 11:43 p.m. |
| PDg | Predicate description generation | batch_69cc5cfddef48190aee764ee7b25bae9 |
completed | March 31, 2026, 11:47 p.m. |
Created at: March 30, 2026, 6:40 p.m.