Triple
T25265439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woizero |
E633417
|
entity |
| Predicate | socialStatusIndicated |
P62272
|
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: [Woizero, socialStatusIndicated, nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialStatusIndicated Context triple: [Woizero, socialStatusIndicated, nobility]
-
A.
possibleSocialStatus
Indicates that one entity may hold, attain, or be associated with a particular social status in relation to another context or system.
-
B.
subjectSocialStatus
chosen
Indicates the social standing or rank that the subject holds within a society or group.
-
C.
socialCondition
Indicates the social or societal circumstances, status, or environment affecting an entity at a given time.
-
D.
socialStatusRequirement
Indicates that a certain social rank or status level is required for an entity to participate in, access, or be eligible for a given relationship or action.
-
E.
statusInCommunity
Indicates the social standing, role, or level of acceptance an entity holds within 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 1:16 p.m.