Triple
T11472276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Investigation Discovery |
E271937
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | ID |
E927360
|
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: ID | Statement: [Investigation Discovery, alsoKnownAs, ID]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ID Context triple: [Investigation Discovery, alsoKnownAs, ID]
-
A.
ID
ID is the two-letter United States Postal Service abbreviation for the state of Idaho.
-
B.
ID
ID is the ISO 3166-1 alpha-2 country code for Indonesia, a Southeast Asian nation made up of thousands of islands.
-
C.
ID
chosen
ID is an American true crime–focused television network known for its documentaries and docudramas about real criminal cases and investigations.
-
D.
UID
UID is a scholarly work that examines the variety and functioning of institutions within economic and social systems.
-
E.
Uid
Uid is a Symfony component that provides tools for generating and working with unique identifiers such as UUIDs and ULIDs in PHP applications.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8294b3f388190a587c358313f7260 |
completed | April 9, 2026, 10:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e6042507c4819096afc2839fda186d |
completed | April 20, 2026, 10:47 a.m. |
Created at: April 8, 2026, 9:35 p.m.