Triple
T12574714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 90-543 |
E300176
|
entity |
| Predicate | typeOfSystemCreated |
P12092
|
FINISHED |
| Object | intercontinental network of trails |
—
|
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: intercontinental network of trails | Statement: [Public Law 90-543, typeOfSystemCreated, intercontinental network of trails]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfSystemCreated Context triple: [Public Law 90-543, typeOfSystemCreated, intercontinental network of trails]
-
A.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
B.
systemTypeOperated
Indicates that an entity operates, controls, or runs a particular type of system.
-
C.
establishedSystem
chosen
Indicates that an entity has created, set up, or formally put into operation a particular system or structured arrangement.
-
D.
systemName
Indicates that an entity has a specific system-level name or identifier assigned to it.
-
E.
typeOfDeployment
Indicates the specific manner or configuration in which something (such as a system, application, or resource) is deployed or made operational.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9550d84908190aea0f50055f6d92e |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95414692881909c52a1de7d224b44 |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 4:46 p.m.