Triple
T8460660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biainili |
E200029
|
entity |
| Predicate | scriptInfluencedBy |
P77309
|
FINISHED |
| Object | Assyrian cuneiform |
—
|
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: Assyrian cuneiform | Statement: [Biainili, scriptInfluencedBy, Assyrian cuneiform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptInfluencedBy Context triple: [Biainili, scriptInfluencedBy, Assyrian cuneiform]
-
A.
scriptInfluence
chosen
Indicates that one script affects, shapes, or alters the behavior, outcome, or characteristics of another entity (such as another script, process, or system).
-
B.
spinOffInfluence
Indicates that one entity has influenced the creation, direction, or characteristics of another entity that is derived from it as a spin-off.
-
C.
influencedWork
Indicates that one work has had a significant impact on the creation, style, content, or development of another work.
-
D.
influencedByCurrent
Indicates that something’s state, behavior, or outcome is affected or determined by the current conditions, context, or situation.
-
E.
influenced
Indicates that one entity has affected, shaped, or altered another entity’s state, behavior, or characteristics.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49fca788190a8728ff74f4d26f5 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.