Triple
T4279308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PL/Tcl |
E97111
|
entity |
| Predicate | untrustedVariantAllows |
P29002
|
FINISHED |
| Object | full Tcl functionality |
—
|
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: full Tcl functionality | Statement: [PL/Tcl, untrustedVariantAllows, full Tcl functionality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: untrustedVariantAllows Context triple: [PL/Tcl, untrustedVariantAllows, full Tcl functionality]
-
A.
securedVariant
Indicates that one entity is a security-enhanced or more protected version of another entity.
-
B.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
C.
supportsUnregisteredUse
chosen
Indicates that an entity allows or enables the use of something without requiring prior registration or formal enrollment.
-
D.
cannotVeto
Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by another entity.
-
E.
trustAnchoredVia
Indicates that a relationship of trust is established or justified through a specific intermediary or anchoring mechanism (such as a trusted authority, key, or certificate).
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b350367da48190b735deef9b5d2d2e |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.