Triple
T23946018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tangents (clavichord) |
E602915
|
entity |
| Predicate | inContactWith |
P19362
|
FINISHED |
| Object | clavichord strings |
—
|
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: clavichord strings | Statement: [Tangents (clavichord), inContactWith, clavichord strings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inContactWith Context triple: [Tangents (clavichord), inContactWith, clavichord strings]
-
A.
contactWith
chosen
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
B.
hasKontakion
Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
-
C.
hasContactInfluenceFrom
Indicates that one entity’s state, behavior, or properties are directly affected or altered through physical or direct contact with another entity.
-
D.
earlyContact
Indicates that one entity initiates contact with another earlier than a typical, expected, or reference time.
-
E.
hasContactState
Indicates that an entity is currently in a specific state or condition regarding its physical or communicative contact with 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d02dd0cc8190b32eb86bdfe0bf9a |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:13 p.m.