Triple
T38276595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bryges |
E1021974
|
entity |
| Predicate | possibleConnectionTo |
P164763
|
FINISHED |
| Object | early Macedonian region |
—
|
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: early Macedonian region | Statement: [Bryges, possibleConnectionTo, early Macedonian region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleConnectionTo Context triple: [Bryges, possibleConnectionTo, early Macedonian region]
-
A.
hasConnectionPotential
chosen
Indicates that there exists a possibility or capacity for a meaningful connection or relationship to form between the entities.
-
B.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
-
C.
connectionTo
Indicates a relationship in which one entity is linked, associated, or otherwise related to another entity.
-
D.
compatibleConnection
Indicates that two entities can be connected or used together without conflict, supporting proper operation or interaction.
-
E.
notConnectedBy
Indicates that there is no direct link, path, or relationship connecting the referenced entities.
- 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_69f76df0cddc81908d16c1556ff4097f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:30 p.m.