Triple
T30123382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Merula |
E765618
|
entity |
| Predicate | usedBySocialStatus |
P181066
|
FINISHED |
| Object | Roman aristocracy |
—
|
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: Roman aristocracy | Statement: [Merula, usedBySocialStatus, Roman aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedBySocialStatus Context triple: [Merula, usedBySocialStatus, Roman aristocracy]
-
A.
subjectSocialStatus
Indicates the social standing or rank that the subject holds within a society or group.
-
B.
socialStatusOrigin
Indicates the source or basis from which an entity’s social status is derived or determined.
-
C.
possibleSocialStatus
Indicates that one entity may hold, attain, or be associated with a particular social status in relation to another context or system.
-
D.
hasSocialIdentity
Indicates that an entity possesses or is associated with a particular social identity, such as a role, group membership, or socially recognized status.
-
E.
inUniverseSocialStatus
Indicates the social rank or standing an entity holds within a specific fictional or defined universe.
- 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_69f2247716748190ae4f16998f49ddf1 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: April 29, 2026, 7:13 p.m.