Triple
T36646118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patterson family |
E904721
|
entity |
| Predicate | hasTypeOfConnection |
P62886
|
FINISHED |
| Object | historical ties |
—
|
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: historical ties | Statement: [Patterson family, hasTypeOfConnection, historical ties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfConnection Context triple: [Patterson family, hasTypeOfConnection, historical ties]
-
A.
hasNoConnectionType
Indicates that there is explicitly no defined type or category of connection between the related entities.
-
B.
hasConnection
Indicates that there exists a link, association, or relationship between two entities.
-
C.
hasModeConnection
chosen
Indicates a relationship where one entity is linked to another through a specific mode, method, or type of connection.
-
D.
hasConnector
Indicates that one entity is linked or joined to another entity through a connector or connecting element.
-
E.
hasPortConnection
Indicates that one entity is linked to another via a port or interface through which data, power, or signals can be transmitted.
- 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_69f76e6d3a3c81909db73eda9e0516bd |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffab5adf2c819084700c5ea34615bf |
completed | May 9, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69ffaabffa208190b5214ca17cc8a5ea |
completed | May 9, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.