Triple
T13221669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Servius |
E314768
|
entity |
| Predicate | usedByClass |
P108592
|
FINISHED |
| Object | Roman patricians |
—
|
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: Roman patricians | Statement: [Servius, usedByClass, Roman patricians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByClass Context triple: [Servius, usedByClass, Roman patricians]
-
A.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
-
B.
usedByModel
Indicates that something (such as a resource, method, or component) is utilized or consumed by a particular model.
-
C.
usedInMethod
Indicates that something (such as a component, variable, or resource) is utilized or referenced within the execution or implementation of a particular method.
-
D.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
E.
areUsedBy
Indicates that certain entities serve as tools, resources, or means that are utilized or employed by other entities.
- 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_69d806affc688190a25b6ccc588e9c72 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf581508190883033f0c961736a |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
| PDg | Predicate description generation | batch_69d98c959ba08190adf29dc0c4e1fca6 |
completed | April 10, 2026, 11:49 p.m. |
Created at: April 9, 2026, 9:18 p.m.