Triple
T9027219
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FSL |
E216076
|
entity |
| Predicate | underlyingSpinOffCompleted |
P63674
|
FINISHED |
| Object | 2004 |
—
|
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: 2004 | Statement: [FSL, underlyingSpinOffCompleted, 2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underlyingSpinOffCompleted Context triple: [FSL, underlyingSpinOffCompleted, 2004]
-
A.
underlyingCommencedOperations
Indicates that the referenced underlying entity has begun its operational activities or business functions.
-
B.
closureCompleted
Indicates that a previously initiated closure process or shutdown has been fully and successfully completed.
-
C.
completedAlongside
Indicates that one action, task, or process was completed at the same time and in coordination with another.
-
D.
underlyingCompanyStatus
Indicates the current operational or legal status of the referenced underlying company in the context of the relationship or transaction.
-
E.
isCompleteOn
chosen
Indicates that an activity, task, or process has been fully finished or achieved by a specific point in time or on a specific date.
- 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7eb5b881908ace0c3327f06161 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 7:07 p.m.