Triple
T16436571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fool for Your Loving |
E399192
|
entity |
| Predicate | hasKeyApprox |
P122783
|
FINISHED |
| Object | E minor |
—
|
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: E minor | Statement: [Fool for Your Loving, hasKeyApprox, E minor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKeyApprox Context triple: [Fool for Your Loving, hasKeyApprox, E minor]
-
A.
hasApproximateEntryCount
Indicates that an entity is associated with a number representing an estimated or non-exact count of its entries.
-
B.
hasApproximateMemberCount
Indicates that an entity is associated with a group or collection for which only an estimated or non-exact number of members is known.
-
C.
hasApproximateValue
Indicates that one entity’s value is close to, but not exactly equal to, the value of another entity within an acceptable margin of error.
-
D.
hasKeyPrediction
Indicates that one entity contains or provides a primary or most important predicted value or outcome for another entity.
-
E.
hasKeyStrait
Indicates that one entity possesses or controls a strategically important strait that is crucial for access, passage, or connectivity to another entity.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32ba224988190b7cccc42f35e54de |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24556c1348190902a4d116c3137d9 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:10 a.m.