Triple
T8002129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acapella |
E186273
|
entity |
| Predicate | isTitleStylizedAs |
P18055
|
FINISHED |
| Object | Acapella |
—
|
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: Acapella | Statement: [Acapella, isTitleStylizedAs, Acapella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTitleStylizedAs Context triple: [Acapella, isTitleStylizedAs, Acapella]
-
A.
isTitleFor
Indicates that one entity serves as the official title or name designation for another entity.
-
B.
includesTitleStyle
chosen
Indicates that one entity incorporates or specifies a particular style or formatting for a title associated with it.
-
C.
mayBeTitled
Indicates that an entity can optionally bear or be assigned a particular title, but is not required to have it.
-
D.
usesTitle
Indicates that one entity refers to or addresses another entity using a specific title or formal designation.
-
E.
hasOrdinaryTitle
Indicates that an entity holds a standard, non-noble or non-honorific title associated with its role or position.
- 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_69ca82aaaf24819084b94d18f699ba53 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3cf2918081909ee0afab11caed63 |
completed | March 31, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:18 p.m.