Triple
T24787880
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Finley railway precinct |
E620166
|
entity |
| Predicate | relationshipToTownship |
P160816
|
FINISHED |
| Object | supported growth of Finley township |
—
|
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: supported growth of Finley township | Statement: [Finley railway precinct, relationshipToTownship, supported growth of Finley township]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToTownship Context triple: [Finley railway precinct, relationshipToTownship, supported growth of Finley township]
-
A.
relationshipToTownship
chosen
Indicates the specific type of relationship or association that an entity has with a particular township.
-
B.
landRelation
Indicates a spatial or ownership-based relationship between entities and a specific piece or area of land.
-
C.
relationshipToVillagers
Indicates the nature or type of relationship that an entity has with the villagers.
-
D.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
E.
typeOfMunicipalRelationship
Indicates a formal type or category of administrative or cooperative relationship that exists between municipalities.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f60c3b09488190ade1b69ff7f0df0e |
completed | May 2, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f60b8461ac81908c5bd3d73eed59f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 18, 2026, 4:46 a.m.