Triple
T9727135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloc Party |
E235641
|
entity |
| Predicate | hasSingle |
P3282
|
FINISHED |
| Object | Mercury |
E18768
|
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: Mercury | Statement: [Bloc Party, hasSingle, Mercury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mercury Context triple: [Bloc Party, hasSingle, Mercury]
-
A.
Mercury
Mercury was an American automobile marque of the Ford Motor Company known for producing mid-priced cars positioned between Ford and Lincoln.
-
B.
Mercury
chosen
Mercury is the smallest and innermost planet in our Solar System, known for its extreme temperature variations and heavily cratered surface.
-
C.
Mercury
Mercury is the Roman god of commerce, communication, and travel, often depicted as a swift messenger of the gods.
-
D.
Mercuri
Mercuri is the surname of Brazilian singer, songwriter, and performer Daniela Mercury, a prominent figure in axé and pop music.
-
E.
Merkur
Merkur was a short-lived automotive marque created by Ford in the 1980s to sell European-designed performance and luxury cars in the North American market.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e7af544819090a8a1adec41943c |
completed | April 1, 2026, 10:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19fb208a48190864f8f085da83db7 |
completed | April 4, 2026, 11:33 p.m. |
Created at: March 30, 2026, 8:21 p.m.