Triple
T30553231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maryland–Virginia maritime boundary |
E777621
|
entity |
| Predicate | basisInDocument |
P4593
|
FINISHED |
| Object | Compact of 1785 |
—
|
NE NERFINISHED |
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: Compact of 1785 | Statement: [Maryland–Virginia maritime boundary, basisInDocument, Compact of 1785]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisInDocument Context triple: [Maryland–Virginia maritime boundary, basisInDocument, Compact of 1785]
-
A.
basisDefinition
Indicates that one entity serves as the foundational explanation, principle, or justification upon which another entity is defined or established.
-
B.
basisType
Indicates the type or category of foundational support or underlying structure on which something is based.
-
C.
basedOnText
chosen
Indicates that something is derived, adapted, or developed from a specific text source.
-
D.
basingConcept
Indicates that one concept serves as the foundational basis or underlying rationale for another concept.
-
E.
hasBaseOn
Indicates that one entity is supported by, rests upon, or is structurally or conceptually founded on another entity.
- 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_69f2249e19108190a458ab446096bf22 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f688d0e3ac81908b558f2b3ac9124d |
completed | May 2, 2026, 11:29 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:20 p.m.