Triple
T17677372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clojure core.async |
E440673
|
entity |
| Predicate | providesPrimitive |
P107341
|
FINISHED |
| Object | channel |
—
|
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: channel | Statement: [Clojure core.async, providesPrimitive, channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesPrimitive Context triple: [Clojure core.async, providesPrimitive, channel]
-
A.
hasPrimitive
chosen
Indicates that an entity is composed of, defined by, or associated with one or more basic, indivisible components or elements.
-
B.
usesPrimitiveType
Indicates that one entity employs or relies on a specified primitive data type in its definition or implementation.
-
C.
providesProperty
Indicates that one entity supplies, grants, or makes a particular property or attribute available to another entity.
-
D.
hasPrimitiveRelation
Indicates a basic, direct relationship between entities that is not derived from or dependent on any other relations.
-
E.
isPrimaryTypeAvailable
Indicates whether a primary or main type associated with an entity is currently available or defined.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46f6e959c819092d9d33e79bd51f7 |
completed | April 19, 2026, 6 a.m. |
| PD | Predicate disambiguation | batch_69e3cde3673c8190a889e14ba1f07dc1 |
completed | April 18, 2026, 6:30 p.m. |
Created at: April 10, 2026, 10:01 a.m.