Triple
T11327077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connecticut College |
E268247
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | Conn |
E301095
|
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: Conn | Statement: [Connecticut College, abbreviation, Conn]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Conn Context triple: [Connecticut College, abbreviation, Conn]
-
A.
Conn
chosen
Conn is an Irish given name of ancient Gaelic origin, often associated with meanings like "chief" or "wisdom" and borne by several legendary and historical figures in Ireland.
-
B.
Connection
"Connection" is a music release by American singer and actor Jacob Latimore, showcasing his blend of contemporary R&B and pop influences.
-
C.
Con
Con is a common diminutive or nickname for the given name Conrad.
-
D.
CON
CON is a Nigerian national honor post-nominal indicating a recipient of the Commander of the Order of the Niger.
-
E.
CON
CON is the stock ticker symbol for Continental AG, a major German automotive parts manufacturer and tire producer.
- 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_69d6aacb1f0881908c84a349fd1be047 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9e2253881909518cad0f12ef612 |
completed | April 9, 2026, 6:03 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e52608b7348190875597513ca1a995 |
completed | April 19, 2026, 6:59 p.m. |
Created at: April 8, 2026, 9:32 p.m.