Triple
T4192762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bravo text editor |
E89072
|
entity |
| Predicate | hasTypeOfEditing |
P43815
|
FINISHED |
| Object | direct manipulation of formatted text |
—
|
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: direct manipulation of formatted text | Statement: [Bravo text editor, hasTypeOfEditing, direct manipulation of formatted text]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfEditing Context triple: [Bravo text editor, hasTypeOfEditing, direct manipulation of formatted text]
-
A.
hasEditorType
Indicates that an entity has an associated kind or category of editor responsible for reviewing or modifying it.
-
B.
hasEditingModel
Indicates that one entity is associated with another entity that serves as its editing or modification model.
-
C.
hasEditionType
Indicates that one entity is a specific edition type or format classification of another entity (such as a work, publication, or product).
-
D.
hasEditorScripting
Indicates that an entity provides or supports scripting capabilities specifically for editing or editor-related functionality.
-
E.
hasEditingStyle
chosen
Indicates that one entity possesses or is characterized by a particular manner or approach to editing.
- 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_69aed9569a4481908b6c1fcec2a11e21 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af04b009dc8190abda3f149a5b16fa |
completed | March 9, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69af01935064819096b7619f42e164dd |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:46 p.m.