Triple
T30580440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Border Tribe |
E778366
|
entity |
| Predicate | battleMount |
P57192
|
FINISHED |
| Object | armored war rhinoceroses |
—
|
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: armored war rhinoceroses | Statement: [Border Tribe, battleMount, armored war rhinoceroses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleMount Context triple: [Border Tribe, battleMount, armored war rhinoceroses]
-
A.
battleTarget
Indicates that one entity is the chosen opponent or objective that another entity is engaging or intends to engage in battle.
-
B.
mountOf
chosen
Indicates that one entity serves as the mount or riding animal/creature used by another entity.
-
C.
battleCryAssociated
Indicates a relationship where a specific battle cry is linked or attributed to a particular entity, such as a person, group, or event.
-
D.
runnerMounting
Indicates a relationship where a runner is being attached, installed, or positioned onto another object or surface.
-
E.
combatBy
Indicates a relationship where one entity engages in combat or fighting through the agency, actions, or involvement of 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6894176d0819096fe66b9baab66f1 |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:23 p.m.