Triple

T2340248
Position Surface form Disambiguated ID Type / Status
Subject Land Ordinance of 1785 E45008 entity
Predicate reservedLandFor P4923 FINISHED
Object public schools 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: public schools | Statement: [Land Ordinance of 1785, reservedLandFor, public schools]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reservedLandFor
Context triple: [Land Ordinance of 1785, reservedLandFor, public schools]
  • A. reservedFor chosen
    Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
  • B. requiredShareOfLand
    Indicates the proportion or amount of land that must be allocated or possessed to satisfy a specified requirement or rule.
  • C. publicLandProtection
    Indicates that a piece of land is subject to legal or formal measures intended to conserve, preserve, or restrict its use for public benefit.
  • D. isPublicLand
    Indicates that a given area of land is owned or managed by a government or public authority and is accessible or designated for use by the general public.
  • E. reserves
    Indicates that an entity has arranged in advance to hold or secure something for future use or access.
  • 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_69a88917935081909b755dbf38e81024 completed March 4, 2026, 7:33 p.m.
NER Named-entity recognition batch_69abc6f75d888190a2e41edaa532e83f completed March 7, 2026, 6:34 a.m.
PD Predicate disambiguation batch_69abc594087c819098100a10c5478a4b completed March 7, 2026, 6:28 a.m.
Created at: March 4, 2026, 7:52 p.m.