Triple
T29939043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSR 3 |
E760443
|
entity |
| Predicate | initiallySupportedIn |
P44871
|
FINISHED |
| Object | Forspoken |
—
|
NE NERFINISHED |
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: Forspoken | Statement: [FSR 3, initiallySupportedIn, Forspoken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallySupportedIn Context triple: [FSR 3, initiallySupportedIn, Forspoken]
-
A.
firstSupportedBy
Indicates that an entity is initially upheld, enabled, or made possible by another entity that provides its primary support.
-
B.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
C.
previouslySupported
Indicates that an entity provided support to another entity at some time in the past, but not necessarily in the present.
-
D.
previouslySupportedVersion
Indicates that one entity was a supported version of another entity at some time in the past but is no longer the current supported version.
-
E.
introducedSupportFor
chosen
Indicates that one entity initiated or implemented backing, assistance, or endorsement for another entity or concept.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 29, 2026, 6:21 p.m.