Triple
T8630819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCS3 |
E204395
|
entity |
| Predicate | BCS1Relation |
P33476
|
FINISHED |
| Object | BCS1 designates the smaller A220‑100 variant |
—
|
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: BCS1 designates the smaller A220‑100 variant | Statement: [BCS3, BCS1Relation, BCS1 designates the smaller A220‑100 variant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BCS1Relation Context triple: [BCS3, BCS1Relation, BCS1 designates the smaller A220‑100 variant]
-
A.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
-
B.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
C.
keyRelation
Indicates a functional or defining association where one entity serves as a key or primary reference for accessing, identifying, or organizing another entity.
-
D.
stepRelation
Indicates a relationship where one entity is a step-relative of another, such as a stepparent, stepchild, or stepsibling connection.
-
E.
hasRelation
chosen
Indicates that there exists some specified relationship or association between two entities.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5730309081909a9a0256c9bf5f8f |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc455906f8819082edd79cb4a1cf28 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.