Triple
T33893453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Wisconsin Airport |
E868837
|
entity |
| Predicate | isJointlyOwnedBy |
P2507
|
FINISHED |
| Object | Marathon County |
—
|
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: Marathon County | Statement: [Central Wisconsin Airport, isJointlyOwnedBy, Marathon County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isJointlyOwnedBy Context triple: [Central Wisconsin Airport, isJointlyOwnedBy, Marathon County]
-
A.
mayBeManagedJointlyWith
Indicates that an entity can be administered, controlled, or overseen together with another entity as part of a shared or coordinated management arrangement.
-
B.
propertyOwnedWithSpouse
Indicates that a property is jointly owned by an individual together with their spouse.
-
C.
sharesCustodyWith
Indicates that two or more parties jointly hold legal responsibility and decision-making authority for the care and upbringing of the same dependent, typically a child.
-
D.
isSharedBy
chosen
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
E.
isSharedByFamily
Indicates that something is commonly used, owned, or enjoyed by multiple members of the same family.
- 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_69f34996761c8190864e42f7c9cf215b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.