Triple
T34050772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angel Clare |
E873216
|
entity |
| Predicate | hasStringArrangements |
P200285
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Angel Clare, hasStringArrangements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStringArrangements Context triple: [Angel Clare, hasStringArrangements, true]
-
A.
hasMultipleArrangements
Indicates that an entity can exist or be configured in more than one distinct arrangement or setup.
-
B.
usesStringArrangement
Indicates that one entity employs or relies on a particular configuration or ordering of strings (such as text sequences or character arrays) to perform its function or achieve an outcome.
-
C.
hasAlternativeArrangementsFor
Indicates that one entity provides or specifies substitute or backup arrangements that can be used in place of another entity’s primary arrangements.
-
D.
hasMusicalArrangementCharacteristic
Indicates that a musical arrangement possesses a specific characteristic, feature, or quality.
-
E.
hasBrassArrangement
Indicates that something includes or is associated with a musical arrangement specifically written for brass instruments.
- F. None of above. chosen
Provenance (4 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff7eb7189c81909a8f73fbc4c48e02 |
completed | May 9, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69ff7e54e11081908fb5ce10c5aa7b53 |
completed | May 9, 2026, 6:35 p.m. |
| PDg | Predicate description generation | batch_69ff7eb638c48190aeca7b85b9b698ab |
completed | May 9, 2026, 6:36 p.m. |
Created at: May 1, 2026, 1:51 a.m.