Triple
T27063801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Associate in Applied Science |
E685118
|
entity |
| Predicate | canArticulateTo |
P161809
|
FINISHED |
| Object | Bachelor of Technology |
—
|
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: Bachelor of Technology | Statement: [Associate in Applied Science, canArticulateTo, Bachelor of Technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canArticulateTo Context triple: [Associate in Applied Science, canArticulateTo, Bachelor of Technology]
-
A.
canArticulateTo
chosen
Indicates that one entity is able to clearly express or communicate something to another entity.
-
B.
articulatesTo
Indicates that one part connects or joins to another part at a joint that allows movement between them.
-
C.
hasArticulation
Indicates that one entity possesses or exhibits a specific type or structure of articulation in relation to another entity or system.
-
D.
cannotBeEasilySpokenBy
Indicates that one entity (typically a word, phrase, or name) is difficult for another entity (typically a speaker or group) to pronounce or articulate smoothly.
-
E.
givesSpeechTo
Indicates that one entity delivers a speech or formal address directed toward another entity or audience.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622e734a881908ac15e64575c69d4 |
completed | May 2, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:23 a.m.