Triple
T8891174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VACM |
E211677
|
entity |
| Predicate | tableIncludes |
P63353
|
FINISHED |
| Object | vacmSecurityToGroupTable |
—
|
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: vacmSecurityToGroupTable | Statement: [VACM, tableIncludes, vacmSecurityToGroupTable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tableIncludes Context triple: [VACM, tableIncludes, vacmSecurityToGroupTable]
-
A.
includesClause
Indicates that one entity (typically a document, contract, or statement) contains or incorporates a specific clause as part of its content.
-
B.
tableType
Indicates the specific category or kind of table that an entity is classified as.
-
C.
hasTables
Indicates that an entity possesses or contains one or more tables.
-
D.
includesList
chosen
Indicates that one entity contains or encompasses a specified list of other entities as its elements or members.
-
E.
tableName
Indicates the name assigned to a database table that participates in the described relationship or operation.
- 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_69ca83907954819096d52a245b635841 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc61ba33c48190a657fc4147a326c0 |
completed | April 1, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2aec04819093c932fe51c0f08d |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:54 p.m.