Triple
T33027603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | REST |
E845082
|
entity |
| Predicate | isTextualCommand |
P175706
|
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: [REST, isTextualCommand, True]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTextualCommand Context triple: [REST, isTextualCommand, True]
-
A.
isTextCommand
chosen
Indicates that something functions as a command expressed in text form, intended to trigger an action or behavior.
-
B.
isPlaintextCommand
Indicates that an instruction or command is expressed in unencrypted, human-readable text rather than in encoded or binary form.
-
C.
isPartOfCommand
Indicates that one entity functions as a component, member, or subordinate unit within a larger command structure or authority.
-
D.
containsCommand
Indicates that one entity includes or embeds a command directed at or executable by another entity.
-
E.
typeOfCommand
Indicates that one entity is a specific kind or category of command in relation to another entity.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:23 a.m.