Triple
T4722801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miami |
E104808
|
entity |
| Predicate | UNLocode |
P1800
|
FINISHED |
| Object | USMIA |
E4885
|
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: USMIA | Statement: [Miami, UNLocode, USMIA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: USMIA Context triple: [Miami, UNLocode, USMIA]
-
A.
USMIA
chosen
USMIA is the UN/LOCODE identifier for the port and transport hub of Miami in the United States.
-
B.
USM
USM (User-based Security Model) is the SNMPv3 security framework that provides user-level authentication, privacy (encryption), and access control for Simple Network Management Protocol communications.
-
C.
USM
USM is the commonly used abbreviation for the Federico Santa María Technical University, a prominent Chilean institution known for its strong engineering and science programs.
-
D.
USAIS
USAIS is the U.S. Army’s primary institution for training, educating, and developing infantry soldiers and leaders.
-
E.
NSMIA
NSMIA is a U.S. federal law enacted in 1996 that reallocated regulatory authority between federal and state governments over securities offerings and investment advisers to streamline and modernize securities regulation.
- 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_69bd43ed84648190ae0b7ee8e8d00482 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd642b82008190bb70dd60a4149502 |
completed | March 20, 2026, 3:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be1094fd9c81909e12723394f9ae0a |
completed | March 21, 2026, 3:29 a.m. |
Created at: March 20, 2026, 1:18 p.m.