Triple
T14025524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MARCOS |
E337446
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | MARCOS |
E337446
|
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: MARCOS | Statement: [MARCOS, abbreviation, MARCOS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MARCOS Context triple: [MARCOS, abbreviation, MARCOS]
-
A.
MARCOS
chosen
MARCOS is the Indian Navy’s elite maritime special operations force, trained for high-risk missions such as amphibious warfare, counterterrorism, and covert reconnaissance.
-
B.
MARCO
MARCO is a prominent contemporary art museum in Monterrey, Mexico, known for its modern architecture and rotating exhibitions of national and international artists.
-
C.
Marcio
Marcio is a masculine given name commonly used in Portuguese- and Spanish-speaking countries, derived from the Latin name Marcius.
-
D.
Mateus
Mateus is a Portuguese surname commonly borne by individuals such as Rui Mateus.
-
E.
Maccus
Maccus is an Old Norse–derived given name that served as the historical root for the later surname and given name Maxwell.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa6ca7481908976ce748a1957b1 |
completed | April 14, 2026, 12:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcb655bb34819097fe88ba76464be8 |
completed | May 7, 2026, 3:57 p.m. |
Created at: April 9, 2026, 10:20 p.m.