Triple
T25906030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Privateers 1882 |
E652752
|
entity |
| Predicate | usesSupportStyle |
P30520
|
FINISHED |
| Object | singing |
—
|
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: singing | Statement: [Privateers 1882, usesSupportStyle, singing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSupportStyle Context triple: [Privateers 1882, usesSupportStyle, singing]
-
A.
usedSupport
Indicates that one entity employed or relied on another entity as a means of support or assistance in performing an action or achieving a result.
-
B.
usedStyle
Indicates that one entity employed or applied a particular style, method, or manner associated with another entity.
-
C.
usesAsStyleOf
chosen
Indicates that one entity adopts or applies another entity as a stylistic model, method, or manner of expression.
-
D.
supportsMarkupStyle
Indicates that one entity is capable of handling, rendering, or otherwise working with a specified markup style associated with another entity.
-
E.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f661b58ac48190907b6c6e9ccc2c59 |
completed | May 2, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69f660eea4648190b0d5e24293607813 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 22, 2026, 8:27 a.m.