Triple
T20466078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European transit corridor |
E502051
|
entity |
| Predicate | canBeSubjectOf |
P52935
|
FINISHED |
| Object | international agreements |
—
|
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: international agreements | Statement: [European transit corridor, canBeSubjectOf, international agreements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeSubjectOf Context triple: [European transit corridor, canBeSubjectOf, international agreements]
-
A.
mayBeSubjectOf
chosen
Indicates that an entity has the potential or possibility to serve as the subject in a given relation, event, or statement.
-
B.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
-
C.
basedOnSubjectOf
Indicates that something is derived from, informed by, or constructed using the subject matter or content of another entity.
-
D.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
E.
hasBeenSubjectOf
Indicates that an entity has previously been the focus or target of a particular action, process, or investigation.
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e696aa0794819082c9989b1f7e9f37 |
completed | April 20, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.