Triple
T16321823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Brown Jug |
E396312
|
entity |
| Predicate | sexEligibility |
P15554
|
FINISHED |
| Object | colts and geldings |
—
|
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: colts and geldings | Statement: [Little Brown Jug, sexEligibility, colts and geldings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sexEligibility Context triple: [Little Brown Jug, sexEligibility, colts and geldings]
-
A.
sexStatus
Indicates whether and how a sexual relationship or sexual activity exists or has occurred between the related entities.
-
B.
sexType
Indicates the specific category or type of sexual activity or sexual relationship involved between entities.
-
C.
hasGenderRequirement
chosen
Indicates that a particular role, activity, or context specifies a required or restricted gender for participation or eligibility.
-
D.
hasSexStatus
Indicates that one entity has a particular sexual status or condition in relation to another entity or context.
-
E.
isSingleSex
Indicates that the entity involves or is restricted to only one biological sex or gender, rather than being mixed or coeducational.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b706108190b43a05b784633050 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
Created at: April 10, 2026, 5:06 a.m.