Triple
T9305394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vega signal project |
E223871
|
entity |
| Predicate | signalCharacteristics |
P55008
|
FINISHED |
| Object | highly structured |
—
|
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: highly structured | Statement: [Vega signal project, signalCharacteristics, highly structured]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signalCharacteristics Context triple: [Vega signal project, signalCharacteristics, highly structured]
-
A.
networkCharacteristic
Indicates a relationship where a specific property or feature is attributed to a network or networking context.
-
B.
serviceCharacterization
Indicates how a service is defined, described, or classified in terms of its properties, behavior, or role.
-
C.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
D.
describesCharacteristicOf
Indicates that one entity expresses or specifies a characteristic, feature, or property of another entity.
-
E.
signalProperty
chosen
Indicates that one entity has a specific characteristic, attribute, or feature related to a signal.
- 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1da7c1e08190af19169f5d806cde |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.