Triple
T30345837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archer |
E771866
|
entity |
| Predicate | servantClass |
P168879
|
FINISHED |
| Object | Archer-class |
—
|
NE NERFINISHED |
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: Archer-class | Statement: [Archer, servantClass, Archer-class]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servantClass Context triple: [Archer, servantClass, Archer-class]
-
A.
servedClass
Indicates that one entity provides service or attention specifically to another entity belonging to a particular class or category.
-
B.
hasServant
Indicates that one entity has another entity serving it in a subordinate or attendant role.
-
C.
serviceClass
Indicates the classification or category of service associated with or provided by an entity in the relationship.
-
D.
treatsServants
Indicates how an entity behaves toward or deals with its servants.
-
E.
slaveType
Indicates that one entity is classified as a slave of a particular type or category in relation to another entity.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682073b00819087f197f3937071a5 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f67603526c81908295a1ece8727c66 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676f73c3481909f01fa69851b7298 |
completed | May 2, 2026, 10:13 p.m. |
Created at: April 29, 2026, 7:55 p.m.