Triple
T35426960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American republics |
E1023946
|
entity |
| Predicate | sharesWithEachOther |
P40775
|
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: [American republics, sharesWithEachOther, historical ties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesWithEachOther Context triple: [American republics, sharesWithEachOther, historical ties]
-
A.
sharesWith
Indicates that one entity gives another entity access to or use of something it possesses.
-
B.
sharesValuesWith
Indicates that two entities hold similar or compatible beliefs, principles, or priorities.
-
C.
sharesElementsWith
chosen
Indicates that two entities have one or more elements or components in common.
-
D.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
-
E.
sharesFieldWith
Indicates that two entities are involved in or associated with the same field, discipline, or area of specialization.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0062e6bd788190a7b4f3e5befb5cbb |
completed | May 10, 2026, 10:50 a.m. |
| PD | Predicate disambiguation | batch_6a0061989d188190b4815b2de3e8676f |
completed | May 10, 2026, 10:44 a.m. |
Created at: May 3, 2026, 4:03 p.m.