Triple
T30420697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Ousterhout |
E773894
|
entity |
| Predicate | languageCreatorOf |
P20615
|
FINISHED |
| Object | Tcl |
—
|
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: Tcl | Statement: [John Ousterhout, languageCreatorOf, Tcl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageCreatorOf Context triple: [John Ousterhout, languageCreatorOf, Tcl]
-
A.
lexifierLanguage
Indicates that one language serves as the primary source or base language from which the core vocabulary and structure of another language, typically a pidgin or creole, are derived.
-
B.
languageName
Indicates the specific name assigned to a language in the relationship.
-
C.
languageDesigned
chosen
Indicates that one entity created or developed the language used or associated with another entity.
-
D.
languageOfWorkOrName
Indicates the language in which a work is created or a name is expressed.
-
E.
languageLabel
Indicates the human-readable name or label of a language associated with an entity or resource.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: April 29, 2026, 8:05 p.m.