Triple
T22443487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Subhadrangi |
E554811
|
entity |
| Predicate | hasSocialOrigin |
P11720
|
FINISHED |
| Object | modest origins |
—
|
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: modest origins | Statement: [Subhadrangi, hasSocialOrigin, modest origins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialOrigin Context triple: [Subhadrangi, hasSocialOrigin, modest origins]
-
A.
hasSocialBasisIn
Indicates that something (such as a concept, practice, or phenomenon) is grounded in, derived from, or fundamentally dependent on social structures, interactions, or relationships.
-
B.
hasSocialIdentity
chosen
Indicates that an entity possesses or is associated with a particular social identity, such as a role, group membership, or socially recognized status.
-
C.
hasLikelyOrigin
Indicates that one entity is inferred or believed, with some degree of uncertainty, to be the source or starting point of another entity.
-
D.
hasSocialService
Indicates that an entity provides, offers, or is associated with a social service to another entity or community.
-
E.
hasOriginIn
Indicates that something begins, arises, or is derived from a specified source, place, or cause.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae40f9081908674015beb33f74e |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.