Triple
T18577467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INEB |
E454021
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | INEB |
—
|
NE NERFINISHED |
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: INEB | Statement: [INEB, acronym, INEB]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: INEB Context triple: [INEB, acronym, INEB]
-
A.
INEB
chosen
INEB is a global network that connects socially engaged Buddhists and organizations working on peace, human rights, and environmental and social justice issues.
-
B.
INENR
INENR is the UN/LOCODE identifier assigned to Ennore Port in India for international trade and transport logistics.
-
C.
INCB
INCB is an independent, quasi-judicial monitoring body of the United Nations responsible for overseeing the implementation of international drug control treaties.
-
D.
INE
INE is Chile’s National Statistics Institute, responsible for producing and disseminating official statistical information for the country.
-
E.
INBOM
INBOM is the UN/LOCODE and port code designating Mumbai Port, one of India’s major maritime gateways on the Arabian Sea.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e543cc94f081909b76c3d488ed5637 |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 11:43 a.m.