Triple
T35591073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bonastruc ça Porta Center |
E1028501
|
entity |
| Predicate | BonastrucÇaPortaAlsoKnownAs |
P183430
|
FINISHED |
| Object | Nahmanides |
—
|
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: Nahmanides | Statement: [Bonastruc ça Porta Center, BonastrucÇaPortaAlsoKnownAs, Nahmanides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BonastrucÇaPortaAlsoKnownAs Context triple: [Bonastruc ça Porta Center, BonastrucÇaPortaAlsoKnownAs, Nahmanides]
-
A.
nameInPortuguese
Indicates that an entity is referred to by a specific name when expressed in the Portuguese language.
-
B.
porte
Indicates that an entity carries, wears, or bears another entity (such as an object, attribute, or characteristic).
-
C.
namedForPortmanteauOf
Indicates that something is named using a portmanteau formed by blending parts of two or more other names or words.
-
D.
بنى
Indicates that an entity constructed, built, or established something (such as a structure, building, or similar object).
-
E.
hasOfficialNameInPortuguese
Indicates that an entity has an official name expressed in the Portuguese language.
- 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_69f76e0598dc8190a6a093e904b9aa70 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f7340e4819092a1a47f7028e63f |
completed | May 3, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
| PDg | Predicate description generation | batch_69f79ec14ce08190b22cee0b40d33743 |
completed | May 3, 2026, 7:15 p.m. |
Created at: May 3, 2026, 4:05 p.m.