Triple
T5924175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bs-platform |
E131763
|
entity |
| Predicate | maintainerHistory |
P25617
|
FINISHED |
| Object | originally maintained by Bloomberg engineers and contributors |
—
|
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: originally maintained by Bloomberg engineers and contributors | Statement: [bs-platform, maintainerHistory, originally maintained by Bloomberg engineers and contributors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maintainerHistory Context triple: [bs-platform, maintainerHistory, originally maintained by Bloomberg engineers and contributors]
-
A.
previousMaintainer
chosen
Indicates that one entity formerly held responsibility for maintaining another entity before the current maintainer.
-
B.
historicallyControlledBy
Indicates that an entity was under the control, rule, or governance of another entity during some period in the past.
-
C.
ownershipHistory
Indicates the sequence of past and present owners associated with an entity over time.
-
D.
hasPrimaryMaintainer
Indicates that one entity is the main person or organization responsible for maintaining or overseeing another entity.
-
E.
upgradeHistory
Indicates the record of changes where one version, state, or configuration has been replaced or improved by another over time.
- 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c033541d108190a34d1fde2fe9dacb |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.