Triple
T27755310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C shell |
E701318
|
entity |
| Predicate | notableDerivative |
P88519
|
FINISHED |
| Object | tcsh |
—
|
NE NERFINISHED |
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: tcsh | Statement: [C shell, notableDerivative, tcsh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDerivative Context triple: [C shell, notableDerivative, tcsh]
-
A.
notableDuo
Indicates that two entities are widely recognized together as a famous or significant pair.
-
B.
notableVariation
chosen
Indicates that one entity represents a significant or noteworthy deviation or difference from another entity within a given context.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableNumber
Indicates that a number associated with an entity is distinguished or significant in some notable way (e.g., record-setting, symbolic, or otherwise remarkable).
-
E.
notableRapid
Indicates a relationship where something is recognized as a particularly fast or unusually rapid instance or occurrence.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_6a00262d71488190a769783fb09e5803 |
completed | May 10, 2026, 6:31 a.m. |
| PD | Predicate disambiguation | batch_6a0023985f148190a335a3fb93e9981e |
completed | May 10, 2026, 6:20 a.m. |
Created at: April 27, 2026, 4:23 p.m.