Triple
T10202222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Middle Horizon |
E238908
|
entity |
| Predicate | hasTypeOfInteraction |
P3970
|
FINISHED |
| Object | interregional exchange |
—
|
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: interregional exchange | Statement: [Middle Horizon, hasTypeOfInteraction, interregional exchange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfInteraction Context triple: [Middle Horizon, hasTypeOfInteraction, interregional exchange]
-
A.
hasInteraction
chosen
Indicates that there is some form of interaction or mutual action occurring between the related entities.
-
B.
hasActionType
Indicates that an action or event is classified as belonging to a specific type or category of actions.
-
C.
hasInteractiveActivity
Indicates that an entity includes or is associated with an activity that requires active user participation or engagement.
-
D.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
E.
haveType
Indicates that an entity belongs to or is classified under a specified type or category.
- 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_69ca84e1ea088190b38162e43d4cfa8f |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdee4239c08190b40f5cc19c3db3c7 |
completed | April 2, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69cd7c8b7f348190a585daa70de4d4c8 |
completed | April 1, 2026, 8:14 p.m. |
Created at: March 30, 2026, 9:14 p.m.