Triple
T24332950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quim |
E613295
|
entity |
| Predicate | nameBearersUsuallyHaveLegalName |
P155747
|
FINISHED |
| Object | Joaquim |
—
|
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: Joaquim | Statement: [Quim, nameBearersUsuallyHaveLegalName, Joaquim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameBearersUsuallyHaveLegalName Context triple: [Quim, nameBearersUsuallyHaveLegalName, Joaquim]
-
A.
typicalNameBearers
Indicates that the subject is a common or characteristic name borne by the entities in the object set.
-
B.
hasUnderlyingLegalName
Indicates that an entity is associated with a specific official legal name that underlies or formally represents it.
-
C.
nameBearerType
Indicates the specific role or capacity in which an entity bears or carries a given name (e.g., as a person, place, organization, or other type of name bearer).
-
D.
hasSurnameBearer
Indicates that a particular surname is borne or carried by a specific person or entity.
-
E.
bearerBirthNameOf
Indicates that one entity is the birth name originally given to and borne by another entity.
- 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_69e2d7db6d5c819091194918157a7c1f |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f23db08190b701bb13aef7f10d |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f28b7ff1808190870dfe9af789a1eb |
completed | April 29, 2026, 10:51 p.m. |
Created at: April 18, 2026, 1:56 a.m.