Triple
T5097275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margarida |
E114896
|
entity |
| Predicate | belongsToNameGroup |
P3889
|
FINISHED |
| Object | Margaret family of names |
—
|
LITERAL 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: Margaret family of names | Statement: [Margarida, belongsToNameGroup, Margaret family of names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belongsToNameGroup Context triple: [Margarida, belongsToNameGroup, Margaret family of names]
-
A.
belongsToGroup
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
B.
associatedName
Indicates that one entity has an alternative or related name that is linked or connected to another entity.
-
C.
associatedWithCharacterGroup
Indicates that an entity has a connection or affiliation with a particular group of characters.
-
D.
isRelatedName
chosen
Indicates that one name is connected to another through a variant, derivative, or otherwise non-identical but related naming relationship.
-
E.
belongsToFamily
Indicates that an entity is a member of, or is associated as part of, a specific family group.
- F. None of above.
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_69bd443fc49c819089629c00e311310c |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75669afc81908a8db897fe56eccd |
completed | March 20, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69bd715e06808190931934dc9930f997 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.