Triple
T3883794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DeVry Inc. |
E92888
|
entity |
| Predicate | hasStockTicker |
P1447
|
FINISHED |
| Object | DV |
E92888
|
NE 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: DV | Statement: [DeVry Inc., hasStockTicker, DV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DV Context triple: [DeVry Inc., hasStockTicker, DV]
-
A.
DV
chosen
DV is the stock ticker symbol for DeVry Inc., a for-profit higher education company traded on public markets.
-
B.
DV
DV is the standard abbreviation for *Dei Verbum*, the Second Vatican Council’s Dogmatic Constitution on Divine Revelation.
-
C.
DN
DN is the official vehicle registration code used for the Indian union territory of Dadra and Nagar Haveli and Daman and Diu.
-
D.
DN
DN is a UK postcode area covering Doncaster and surrounding parts of South Yorkshire and Lincolnshire, including North East Lincolnshire.
-
E.
DM
DM is the commonly used abbreviation for the Deutsche Mark, the former official currency of West Germany and later unified Germany before the adoption of the euro.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec9029908190a7b36a3827734db1 |
completed | March 9, 2026, 3:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b512594fa081909ba2afad11f6ea59 |
completed | March 14, 2026, 7:46 a.m. |
Created at: March 9, 2026, 3:20 p.m.