Triple
T32614249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warriors Three |
E833741
|
entity |
| Predicate | notBasedDirectlyOn |
P169322
|
FINISHED |
| Object | specific Norse mythological trio |
—
|
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: specific Norse mythological trio | Statement: [Warriors Three, notBasedDirectlyOn, specific Norse mythological trio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notBasedDirectlyOn Context triple: [Warriors Three, notBasedDirectlyOn, specific Norse mythological trio]
-
A.
doesNotBaseOn
chosen
Indicates that one entity is not derived from, influenced by, or constructed using another entity as a basis.
-
B.
notDirectlyIntegratedWith
Indicates that two entities are not connected or combined through a direct integration or interface.
-
C.
notDirectSpinOffFrom
Indicates that one entity is explicitly not a direct spin-off derived from another entity.
-
D.
notDerivedFrom
Indicates that one entity is explicitly not obtained, inferred, or produced from another entity.
-
E.
notDirectlyAvailableFor
Indicates that an entity cannot be accessed, used, or obtained immediately or without intermediaries, but may be reachable through indirect means or additional steps.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:06 a.m.