Triple
T22444636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CJS |
E554833
|
entity |
| Predicate | dependencyGraph |
P148224
|
FINISHED |
| Object | resolved at runtime |
—
|
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: resolved at runtime | Statement: [CJS, dependencyGraph, resolved at runtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dependencyGraph Context triple: [CJS, dependencyGraph, resolved at runtime]
-
A.
dependencyModel
Indicates a relationship where one entity relies on, is conditioned by, or is structured according to another entity within a dependency framework or model.
-
B.
dependency
Indicates that one entity relies on, is conditioned by, or cannot function or exist properly without another entity.
-
C.
usesDigraph
Indicates that one entity employs or represents information using a directed graph structure, where relationships have a specified direction.
-
D.
crownDependencyOf
Indicates that one entity is a Crown dependency that is self-governing but under the sovereignty or jurisdiction of another entity (typically a state or monarch).
-
E.
graphAnalogue
Indicates that one entity serves as a graph-theoretic counterpart or structural analogue of another entity.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae517208190924a7968723f55ef |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.