Triple
T15810203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivertowns |
E383325
|
entity |
| Predicate | notOfficially |
P13450
|
FINISHED |
| Object | incorporated municipality |
—
|
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: incorporated municipality | Statement: [Rivertowns, notOfficially, incorporated municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notOfficially Context triple: [Rivertowns, notOfficially, incorporated municipality]
-
A.
notOfficialIn
Indicates that an entity does not hold an official role, status, or position within a specified organization, group, or jurisdiction.
-
B.
notOfficialNameOf
chosen
Indicates that a given name or label is used for an entity but is not its official or formally recognized name.
-
C.
notOfficialCodeOf
Indicates that one entity is not the formally recognized or authorized code designation for the other entity.
-
D.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
E.
notOfficialScriptFor
Indicates that a given writing system is explicitly not recognized or used as the official script for a particular language or 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b52aae14819091de08630e7e1d1a |
completed | April 16, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.