Triple
T3057224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iasion |
E60509
|
entity |
| Predicate | symbolicConnection |
P37306
|
FINISHED |
| Object | ploughed field |
—
|
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: ploughed field | Statement: [Iasion, symbolicConnection, ploughed field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolicConnection Context triple: [Iasion, symbolicConnection, ploughed field]
-
A.
symbolicContinuity
Indicates that there is a consistent, ongoing use or preservation of the same symbols or symbolic forms across time, contexts, or instances.
-
B.
ridgeConnection
Indicates a structural relationship where one ridge is connected or linked to another ridge, forming a continuous or associated ridge feature.
-
C.
connectionTo
chosen
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
D.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
E.
connectedLine
Indicates that two entities are joined by a continuous line or linear connection.
- 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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9e162d148190969fb422a45d052c |
completed | March 8, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69ad962326e081909d5521c3d3ea3158 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.