Triple
T909760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montenegro |
E19630
|
entity |
| Predicate | vehicleRegistrationCode |
P1173
|
FINISHED |
| Object | MNE |
E107431
|
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: MNE | Statement: [Montenegro, vehicleRegistrationCode, MNE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MNE Context triple: [Montenegro, vehicleRegistrationCode, MNE]
-
A.
MNE
MNE is the standard abbreviation used for the Maine Celtics, an NBA G League basketball team based in Portland, Maine.
-
B.
MNE
chosen
MNE is the three-letter ISO 3166-1 alpha-3 country code assigned to Montenegro.
-
C.
MCA
MCA was a major American record label and entertainment company known for signing prominent artists and producing a wide range of popular music releases.
-
D.
TMS
TMS (Test Mode Select) is the JTAG control signal used to navigate the TAP (Test Access Port) state machine in IEEE 1149.1 boundary-scan operations.
-
E.
EMA
EMA is the European Union’s regulatory authority responsible for the scientific evaluation, supervision, and safety monitoring of medicines.
- 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_69a4939f91a08190ba68c2c81eab90fe |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b2dca5208190bc9f17cd9dd6a98f |
completed | March 1, 2026, 9:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7cf5c4acc8190a0f72ca30f187ed1 |
completed | March 4, 2026, 6:21 a.m. |
Created at: March 1, 2026, 7:39 p.m.