Triple
T247763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F |
E5075
|
entity |
| Predicate | underlyingFoundedIn |
P1672
|
FINISHED |
| Object | 1903 |
—
|
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: 1903 | Statement: [F, underlyingFoundedIn, 1903]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingFoundedIn Context triple: [F, underlyingFoundedIn, 1903]
-
A.
foundedUnder
Indicates that an entity was established or created during the tenure, authority, or jurisdiction of another entity (such as a leader, regime, or governing body).
-
B.
countryOfUnderlyingCompany
Indicates the country in which the underlying company associated with an entity is legally established or primarily based.
-
C.
foundedAs
Indicates the original name or form under which an organization, institution, or entity was first established.
-
D.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
E.
foundedInJurisdiction
chosen
Indicates that an entity was established or legally founded within the authority or territorial scope of a specific jurisdiction.
- 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d154ebc819087a5c9dc4f62ff44 |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b64ea3081908de626a0e1445bdb |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.