Triple
T30357887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sony A-mount |
E772195
|
entity |
| Predicate | hasElectronicContacts |
P88194
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Sony A-mount, hasElectronicContacts, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasElectronicContacts Context triple: [Sony A-mount, hasElectronicContacts, yes]
-
A.
hasContactMethod
Indicates that an entity has a specific way or channel through which it can be contacted.
-
B.
hasElectronicCharacter
Indicates that something possesses qualities, properties, or behavior associated with electronics or electronic systems.
-
C.
hasKontakion
Indicates that an entity is associated with or possesses a specific kontakion, i.e., a particular liturgical hymn or chant.
-
D.
hasElectronicEffect
Indicates that one entity exerts or contributes an electronic influence or effect on another entity within a specified context.
-
E.
hasElectronicsFeature
chosen
Indicates that an entity possesses or is characterized by a specific electronic-related feature or capability.
- 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_69f2248c6f5c8190a6177842bf791a3c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 29, 2026, 7:57 p.m.