Triple
T17894210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RVSN |
E447391
|
entity |
| Predicate | establishedAsSeparateBranch |
P5427
|
FINISHED |
| Object | 1959 |
—
|
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: 1959 | Statement: [RVSN, establishedAsSeparateBranch, 1959]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: establishedAsSeparateBranch Context triple: [RVSN, establishedAsSeparateBranch, 1959]
-
A.
hadSeparateBranch
Indicates that one entity maintained a distinct, independent branch or subdivision separate from another entity.
-
B.
establishedAsBranchBy
Indicates that one entity was created or designated as a branch or subsidiary by another entity.
-
C.
dissolvedAsIndependentBranch
Indicates that an entity, previously functioning as an independent branch, has been formally dissolved or ceased to exist in that independent capacity.
-
D.
isIndependentBranchOf
Indicates that one branch or subdivision operates autonomously and is not subordinate to the other branch or organization it is associated with.
-
E.
openedAsBranchOf
chosen
Indicates that one entity was established and began operating as a branch or subsidiary location of another entity.
- 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_69d8b9f59bd48190a6fc925a855b8bac |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49d7ccf808190b4c1fd477043bcc8 |
completed | April 19, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e9b77c8190bbfb508f28dfacfa |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:19 a.m.