Triple
T17888765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIT Croatia |
E447258
|
entity |
| Predicate | hasInstructionMode |
P91314
|
FINISHED |
| Object | on-campus |
—
|
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: on-campus | Statement: [RIT Croatia, hasInstructionMode, on-campus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInstructionMode Context triple: [RIT Croatia, hasInstructionMode, on-campus]
-
A.
hasInstructionSet
Indicates that one entity (typically a processor or system) is defined as using or supporting a particular instruction set.
-
B.
instructionMode
chosen
Indicates the method or medium through which an instruction, lesson, or teaching activity is delivered.
-
C.
hasInstructionCache
Indicates that an entity possesses or is equipped with an instruction cache for storing and accessing executable instructions.
-
D.
hasInstructionPrefix
Indicates that one entity provides an initial segment or starting portion that serves as the instruction prefix for another entity.
-
E.
hasModeSystem
Indicates that one entity operates under, or is associated with, a particular mode defined or managed by another system.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49c15f8b08190ac8d134e32d62d18 |
completed | April 19, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:18 a.m.