Triple
T30681357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | antoninianus |
E781058
|
entity |
| Predicate | valueRelationTo |
P28911
|
FINISHED |
| Object | multiple of the as |
—
|
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: multiple of the as | Statement: [antoninianus, valueRelationTo, multiple of the as]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueRelationTo Context triple: [antoninianus, valueRelationTo, multiple of the as]
-
A.
valueRelation
chosen
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
B.
termRelationTo
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
C.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
D.
unitRelation
Indicates a relationship between units, such as how one unit is associated with, derived from, or converted to another.
-
E.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 8:32 p.m.