Triple
T34368307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Foundling |
E882080
|
entity |
| Predicate | associatedWithSettingCountry |
P1083
|
FINISHED |
| Object | England |
E1791
|
NE 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: England | Statement: [A Foundling, associatedWithSettingCountry, England]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSettingCountry Context triple: [A Foundling, associatedWithSettingCountry, England]
-
A.
associatedWithSetting
Indicates that one entity is connected or linked to a particular context, environment, or setting in which it occurs or is relevant.
-
B.
associatedCountryCode
Indicates that there is a relationship linking something to the country identified by the given country code.
-
C.
correspondsToCountry
Indicates that one entity is associated with, matches, or represents a specific country.
-
D.
usesCountry
Indicates that one entity makes use of, operates within, or is functionally associated with a specified country.
-
E.
associatedCountry
chosen
Indicates that there is a relevant connection or linkage between an entity and a specific country, such as origin, operation, or affiliation.
- F. None of above.
Provenance (4 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_69f349be5c9c81908dc726ae1f4c68f2 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37047cd87481909f61fdd49dc24fa0 |
completed | June 20, 2026, 9:22 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:58 a.m.