Triple
T19516852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | East New Jersey |
E488298
|
entity |
| Predicate | usedAssembly |
P38394
|
FINISHED |
| Object | colonial assembly |
—
|
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: colonial assembly | Statement: [East New Jersey, usedAssembly, colonial assembly]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAssembly Context triple: [East New Jersey, usedAssembly, colonial assembly]
-
A.
hasAssembly
Indicates that an entity is composed of, or includes, one or more component parts assembled into a whole.
-
B.
usedComponent
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
-
C.
hadLocalAssembly
chosen
Indicates that an entity hosted or possessed a local-level governing or decision-making assembly within its jurisdiction or area.
-
D.
usedStructure
Indicates that one entity makes use of, relies on, or operates through a particular structure (physical, logical, or organizational) to perform its function or action.
-
E.
isUsedAs
Indicates that one entity serves a particular function, role, or purpose as 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359ca7648190804c4d655170fda3 |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7d0da88190aabf8b5799691fb1 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.