Triple
T18281192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PMAC |
E437866
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | OMAC |
—
|
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: OMAC | Statement: [PMAC, relatedTo, OMAC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OMAC Context triple: [PMAC, relatedTo, OMAC]
-
A.
OMACs
chosen
OMACs are cybernetically enhanced human drones in DC Comics, controlled by the Brother Eye satellite and often used as weapons against superheroes.
-
B.
OAMC
OAMC is the abbreviation for Oman Airports Management Company, the organization responsible for operating and managing major airports in Oman.
-
C.
OAC
OAC is the Amtrak station code for the Oakland Coliseum station serving rail passengers in Oakland, California.
-
D.
OAC
OAC is the commonly used abbreviation for the Ohio Athletic Conference, an NCAA Division III collegiate athletic conference based in Ohio.
-
E.
OAC
OAC is the acronym for Taiwan’s Ocean Affairs Council, the government body responsible for formulating and coordinating the nation’s maritime and ocean-related policies.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50056ea0481908d66bf263ac80c75 |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 10:35 a.m.