Triple
T7219708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Primrose |
E150223
|
entity |
| Predicate | hasSocialStatusAssociation |
P11720
|
FINISHED |
| Object | 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: aristocracy | Statement: [Primrose, hasSocialStatusAssociation, aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSocialStatusAssociation Context triple: [Primrose, hasSocialStatusAssociation, aristocracy]
-
A.
associationStatus
Indicates the current state or condition of an established association or relationship between entities.
-
B.
associatedStatus
Indicates that one entity is linked to or characterized by a particular status or condition.
-
C.
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.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
hasAssociateMember
Indicates that an entity has another entity connected to it in a non-full, typically limited or secondary, membership capacity.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b1a7908190bd215ffb84592e32 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e75f84e481909e7866186ae80cff |
completed | March 27, 2026, 8:23 p.m. |
Created at: March 27, 2026, 2:53 p.m.