Triple
T16181210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marc Márquez |
E392686
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Marc |
E48930
|
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: Marc | Statement: [Marc Márquez, givenName, Marc]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Marc Context triple: [Marc Márquez, givenName, Marc]
-
A.
Marc
chosen
Marc is the given name of Marc Andreessen, the influential American entrepreneur, software engineer, and venture capitalist known for co-creating the Mosaic web browser and co-founding Netscape and Andreessen Horowitz.
-
B.
Marc
Marc is a surname of Germanic origin borne by various individuals, including Maria Marc.
-
C.
Marcus
Marcus is a masculine given name of ancient Roman origin that has been widely used across many cultures and historical periods.
-
D.
Markus
Markus is the given first name of the renowned abstract expressionist painter Mark Rothko.
-
E.
Markus
Markus is a masculine given name of Latin origin, commonly used in various European countries and derived from the name Marcus.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205c92b48190b7125dbbcff3662e |
completed | April 17, 2026, 11:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffff0022148190bc1810e76cf6d994 |
completed | May 10, 2026, 3:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.