Triple
T12983580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the knight without fear and beyond reproach |
E321711
|
entity |
| Predicate | appliedToSocialStatus |
P62272
|
FINISHED |
| Object | nobleman |
—
|
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: nobleman | Statement: [the knight without fear and beyond reproach, appliedToSocialStatus, nobleman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedToSocialStatus Context triple: [the knight without fear and beyond reproach, appliedToSocialStatus, nobleman]
-
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.
hasSocialService
Indicates that an entity provides, offers, or is associated with a social service to another entity or community.
-
C.
subjectSocialStatus
chosen
Indicates the social standing or rank that the subject holds within a society or group.
-
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.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
- 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_69d8076479b8819090afce3591939cdf |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97f2a71a0819098bb6cf8a4b2208a |
completed | April 10, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69d97dbdd94c8190ac4bbecca02dc77b |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:39 p.m.