Triple
T13157459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Institute of Management Technology Ghaziabad |
E312625
|
entity |
| Predicate | hasCell |
P23615
|
FINISHED |
| Object | placement cell |
—
|
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: placement cell | Statement: [Institute of Management Technology Ghaziabad, hasCell, placement cell]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCell Context triple: [Institute of Management Technology Ghaziabad, hasCell, placement cell]
-
A.
hasCells
chosen
Indicates that an entity contains, is composed of, or is associated with one or more cells.
-
B.
hasRow
Indicates that one entity contains, includes, or is associated with a specific row within a structured arrangement such as a table, grid, or dataset.
-
C.
hasCol
Indicates that one entity possesses, contains, or is associated with a particular color.
-
D.
hasCollectionAt
Indicates that a collection or gathering of items, data, or resources is located, stored, or maintained at a specific place or context.
-
E.
hasStudentCells
Indicates that an entity contains, includes, or is associated with one or more cells designated as student cells.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:12 p.m.