Triple
T3363712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bertrando |
E70783
|
entity |
| Predicate | usedBySocialGroup |
P7159
|
FINISHED |
| Object | nobility |
—
|
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: nobility | Statement: [Bertrando, usedBySocialGroup, nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBySocialGroup Context triple: [Bertrando, usedBySocialGroup, nobility]
-
A.
hasSocialGroup
Indicates that an entity belongs to, is associated with, or participates in a particular social group or community.
-
B.
socialGroupInvolved
Indicates that a particular social group participates in, is affected by, or is otherwise involved in the specified event or situation.
-
C.
sociallyIntegratedWith
Indicates that two entities are connected through meaningful social relationships, interactions, or participation within the same social context or community.
-
D.
socialComposition
Indicates the makeup or distribution of different social groups or categories within a population or community.
-
E.
usedByCommunity
chosen
Indicates that something is utilized or adopted collectively by a particular community.
- 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_69ad85a660c48190998489309a3b4869 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb28467b88190bdf70b851bc8efa9 |
completed | March 8, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69ada4317e288190ab7d0f66e9dba65f |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:13 p.m.