Triple
T37461466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Princess Huhuran |
E930926
|
entity |
| Predicate | tribeSynergyClass |
P99994
|
FINISHED |
| Object | Hunter |
—
|
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: Hunter | Statement: [Princess Huhuran, tribeSynergyClass, Hunter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tribeSynergyClass Context triple: [Princess Huhuran, tribeSynergyClass, Hunter]
-
A.
tribeSynergy
Indicates a cooperative or mutually enhancing relationship among members of the same tribe or group, where their combined presence or actions produce greater overall effectiveness than they would individually.
-
B.
classTribeSynergy
chosen
Indicates a synergistic relationship where a character’s class and tribe traits interact to provide combined or enhanced effects.
-
C.
inTribe
Indicates that an entity belongs to, is a member of, or is affiliated with a particular tribe.
-
D.
tribeCharacterization
Indicates how a tribe or tribal group is characterized or described in terms of its defining qualities, attributes, or identity.
-
E.
includesTribe
Indicates that one entity contains, encompasses, or has within it a particular tribe as a member or component.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.