Triple
T4470307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACKTR |
E98477
|
entity |
| Predicate | usesTrustRegion |
P56720
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [ACKTR, usesTrustRegion, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesTrustRegion Context triple: [ACKTR, usesTrustRegion, true]
-
A.
lastTrustTerritory
Indicates that an entity is the final remaining trust territory associated with another entity (such as an administering authority or system of governance).
-
B.
requiresConfidenceOf
Indicates that one entity can only proceed, function, or be accepted if it has sufficient trust, assurance, or belief in the reliability or correctness of another entity.
-
C.
typeOfTrust
Indicates the specific kind or category of trust that characterizes the relationship between entities.
-
D.
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).
-
E.
trustModel
Indicates that one entity relies on or has confidence in the reliability, integrity, or performance of another entity or system.
- F. None of above. chosen
Provenance (4 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_69b3454b4ae481908967426dd37284d6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b356fb69a0819099f0005779f4fcac |
completed | March 13, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69b3563bf4f8819081726cde3a34460b |
completed | March 13, 2026, 12:11 a.m. |
| PDg | Predicate description generation | batch_69b356f9afc48190acb50c45a310e072 |
completed | March 13, 2026, 12:14 a.m. |
Created at: March 12, 2026, 11:34 p.m.