Triple
T4992693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avgad |
E112168
|
entity |
| Predicate | hasTransmissionForm |
P7413
|
FINISHED |
| Object | variant textual form |
—
|
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: variant textual form | Statement: [Avgad, hasTransmissionForm, variant textual form]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransmissionForm Context triple: [Avgad, hasTransmissionForm, variant textual form]
-
A.
transmissionType
chosen
Indicates the method or medium through which something is transmitted or conveyed from one entity to another.
-
B.
hasTraditionalFormIn
Indicates that something possesses a customary or historically established form or representation within a specified context, system, or location.
-
C.
transmittedIn
Indicates that something (such as information, a signal, or a disease) is passed or conveyed within or through a particular medium, environment, or context.
-
D.
hasTransfer
Indicates a relationship where something is moved or conveyed from one entity or location to another.
-
E.
transmission
Indicates the transfer or conveyance of something (such as information, energy, or material) from one entity to another.
- 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_69bd441be7bc8190b530362d427b97d2 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.