Triple
T5414798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffetes |
E121103
|
entity |
| Predicate | saidToBeEquivalentTo |
P6530
|
FINISHED |
| Object | Roman consuls |
—
|
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 consuls | Statement: [Suffetes, saidToBeEquivalentTo, Roman consuls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saidToBeEquivalentTo Context triple: [Suffetes, saidToBeEquivalentTo, Roman consuls]
-
A.
equivalentTo
chosen
Indicates that two entities represent the same concept, value, or state, and can be treated as interchangeable in the given context.
-
B.
equivalentIn
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
C.
hasEquivalent
Indicates that two entities are considered equal in value, meaning, or function within a given context.
-
D.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
E.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bcace08190932fe85e4b4aeffc |
completed | March 20, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69bd8469f5e48190bbe5c8bdfe8925ea |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:05 p.m.