Triple
T3253727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Clive (British Army officer) |
E68245
|
entity |
| Predicate | socialClassification |
P39847
|
FINISHED |
| Object | British gentry |
—
|
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: British gentry | Statement: [George Clive (British Army officer), socialClassification, British gentry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: socialClassification Context triple: [George Clive (British Army officer), socialClassification, British gentry]
-
A.
socialCategory
chosen
Indicates that an entity belongs to, or is classified within, a particular social group, class, or category.
-
B.
socialClassRepresented
Indicates that one entity portrays, embodies, or stands in for the social class or socioeconomic group associated with another entity.
-
C.
areClassifiedBy
Indicates that entities are assigned to one or more categories, types, or classes according to a specified classification scheme.
-
D.
classified
Indicates that one entity has assigned another entity to a specific category, group, or type based on defined criteria.
-
E.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf640fd8819083c3c0cc41db2ffc |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.