Triple
T5894953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AngularJS |
E131078
|
entity |
| Predicate | dataBindingType |
P37577
|
FINISHED |
| Object | two-way |
—
|
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: two-way | Statement: [AngularJS, dataBindingType, two-way]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataBindingType Context triple: [AngularJS, dataBindingType, two-way]
-
A.
dataBusType
Indicates the type or category of data bus used to transfer data between components or systems.
-
B.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another entity.
-
C.
bindingOption
chosen
Indicates a relationship where one entity specifies or constrains how another entity is bound, attached, or associated within a given context or configuration.
-
D.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
E.
bindingOn
Indicates that one party is legally or formally obligated to follow, accept, or be governed by a decision, rule, or agreement established by another.
- 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_69c00857439c819095950754176aa58a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:58 p.m.