Triple
T35481793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackfyre |
E1025488
|
entity |
| Predicate | edgeQuality |
P152176
|
FINISHED |
| Object | extremely sharp |
—
|
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: extremely sharp | Statement: [Blackfyre, edgeQuality, extremely sharp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: edgeQuality Context triple: [Blackfyre, edgeQuality, extremely sharp]
-
A.
edgeType
Indicates the specific kind or category of connection that exists between two related entities.
-
B.
edgeFeature
chosen
Indicates a characteristic or property specifically associated with an edge or boundary within a structure, graph, or spatial configuration.
-
C.
edgeCondition
Indicates a condition or set of criteria that must hold at the boundary or limit of a structure, process, or domain.
-
D.
edgeTreatment
Indicates a relationship where a specific method or process is applied to modify, finish, or protect the edge of an object or material.
-
E.
edgeCoverage
Indicates that one element (such as a test, path, or configuration) covers or exercises a specific edge or connection in a graph or network structure.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79da9f80c8190b0afd8509f28747b |
completed | May 3, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f79617d40481909ba372f94209c08b |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.