Triple
T28470866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-1 |
E720431
|
entity |
| Predicate | supportsConcatenation |
P192432
|
FINISHED |
| Object | STS-1c |
—
|
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: STS-1c | Statement: [STS-1, supportsConcatenation, STS-1c]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsConcatenation Context triple: [STS-1, supportsConcatenation, STS-1c]
-
A.
supportsChaining
Indicates that one entity enables or allows another entity to be linked in sequence with additional similar entities, forming a chain of operations or relationships.
-
B.
designedToCombine
chosen
Indicates that one entity is intentionally created or configured to be merged, integrated, or used together with another entity.
-
C.
canBeAugmentedWith
Indicates that one entity is capable of being enhanced, expanded, or supplemented by another entity.
-
D.
canMerge
Indicates that two or more entities are compatible in such a way that they can be combined into a single unified entity or structure.
-
E.
supportsConjunctConsonants
Indicates that a writing system or orthographic convention allows the formation and use of conjunct consonant clusters (combined consonant characters).
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00ab25c5b48190ad07ff508392ef56 |
completed | May 10, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_6a00a8a5cfc48190bbe97fb2bbd1b947 |
completed | May 10, 2026, 3:47 p.m. |
Created at: April 28, 2026, 2:48 a.m.