Triple
T30301021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friendly Interactive SHell |
E770650
|
entity |
| Predicate | defaultPromptName |
P66254
|
FINISHED |
| Object | fish_prompt |
—
|
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: fish_prompt | Statement: [Friendly Interactive SHell, defaultPromptName, fish_prompt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultPromptName Context triple: [Friendly Interactive SHell, defaultPromptName, fish_prompt]
-
A.
defaultProgramName
Indicates the standard or pre-selected name assigned to a program when no specific name is explicitly provided.
-
B.
defaultNameValue
chosen
Indicates that an entity is assigned a standard or fallback name value used when no specific name has been provided.
-
C.
promptType
Indicates the specific category or style of a prompt that characterizes how an instruction or request is framed or intended to be interpreted.
-
D.
protagonistDefaultName
Indicates that an entity is the default or canonical name assigned to the protagonist in a given work or context.
-
E.
currentName
Indicates the present or most recently assigned name associated with an 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_69f224881b948190b8c4921b250a44a3 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 7:48 p.m.