Triple
T37461741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flamewreathed Faceless |
E930934
|
entity |
| Predicate | overloadValue |
P127096
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Flamewreathed Faceless, overloadValue, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overloadValue Context triple: [Flamewreathed Faceless, overloadValue, 2]
-
A.
hasOverload
Indicates that an entity defines multiple variants (overloads) of the same operation or function, typically distinguished by differing parameters or signatures.
-
B.
takesValueOn
chosen
Indicates that one entity assumes, is assigned, or exhibits a particular value in relation to another entity or context.
-
C.
hasOverloadProtection
Indicates that an entity is equipped with a mechanism or feature that prevents damage or failure due to excessive load or current.
-
D.
overField
Indicates a spatial relationship where one entity is positioned above or extends across the area of a field.
-
E.
variesOver
Indicates that the value, state, or behavior of one entity changes as a function of another entity or parameter.
- 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_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.