Triple
T29411249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman–Sabine relations |
E745898
|
entity |
| Predicate | hasLegendaryElement |
P170938
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Roman–Sabine relations, hasLegendaryElement, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendaryElement Context triple: [Roman–Sabine relations, hasLegendaryElement, yes]
-
A.
hasLegendaryPokémon
Indicates that an entity (such as a location, trainer, or group) possesses, contains, or is associated with at least one Legendary Pokémon.
-
B.
hasLegendaryPlayer
Indicates that an entity (such as a team, club, or organization) is associated with at least one player recognized as legendary.
-
C.
isLegendaryStatus
Indicates that an entity possesses a legendary status, typically signifying exceptional rarity, renown, or significance within a given context.
-
D.
hasCultOrLegend
chosen
Indicates that an entity is associated with, or is the subject of, a cult, myth, or legendary tradition.
-
E.
hasMythicalFigure
Indicates that one entity is associated with, features, or includes a particular mythical or legendary figure.
- 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_69f0a79eb7d081908c67197a5f347e68 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
Created at: April 28, 2026, 2:57 p.m.