Triple
T36557190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcho |
E901727
|
entity |
| Predicate | partnerInDeed |
P186197
|
FINISHED |
| Object | Blanco |
—
|
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: Blanco | Statement: [Marcho, partnerInDeed, Blanco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerInDeed Context triple: [Marcho, partnerInDeed, Blanco]
-
A.
parter
Indicates that two entities are partners, typically engaged in a shared, cooperative, or jointly responsible relationship.
-
B.
partnerInUnionWith
Indicates a mutual partnership or union relationship between two entities, such as a civil, domestic, or similar legally or socially recognized union.
-
C.
deed
Indicates that an entity performs, carries out, or is responsible for a particular action or act.
-
D.
partnerInCreation
Indicates that two or more entities collaborated as partners in bringing something into existence or producing it.
-
E.
partnerInWorkOf
Indicates a collaborative relationship where one entity works together with another on a shared task, project, or professional activity.
- F. None of above. chosen
Provenance (4 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_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:11 p.m.