Triple
T24048229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TANGO |
E595579
|
entity |
| Predicate | customizationOptions |
P139067
|
FINISHED |
| Object | length configurable by number of modules |
—
|
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: length configurable by number of modules | Statement: [TANGO, customizationOptions, length configurable by number of modules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: customizationOptions Context triple: [TANGO, customizationOptions, length configurable by number of modules]
-
A.
customizableFeatures
chosen
Indicates that certain aspects or options of an entity can be modified or configured according to specific preferences or requirements.
-
B.
customizableWith
Indicates that one entity can be modified, configured, or tailored in some way using another entity.
-
C.
customizableBy
Indicates that one entity can be modified, configured, or tailored in some way by another entity.
-
D.
equipmentOption
Indicates that a particular piece or configuration of equipment is available or selected as an option in a given context.
-
E.
aftermarketSupport
Indicates that one entity provides maintenance, service, or assistance for another entity after the initial sale or deployment.
- 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9cd50648190b009e97e5be53e8b |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:18 p.m.