Triple
T37459337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neptulon |
E930878
|
entity |
| Predicate | generatesTribe |
P100010
|
FINISHED |
| Object | Murloc |
—
|
NE NERFINISHED |
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: Murloc | Statement: [Neptulon, generatesTribe, Murloc]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: generatesTribe Context triple: [Neptulon, generatesTribe, Murloc]
-
A.
tribeOrGens
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
-
B.
tribeName
Indicates the name assigned to a tribe in the relationship.
-
C.
introducedTribe
chosen
Indicates that one entity caused a tribe to become known, present, or established to another entity or context for the first time.
-
D.
inTribe
Indicates that an entity belongs to, is a member of, or is affiliated with a particular tribe.
-
E.
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.
- 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_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.