Triple
T27880053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia's Next Top Model |
E705061
|
entity |
| Predicate | contestantEligibility |
P84
|
FINISHED |
| Object | aspiring female models |
—
|
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: aspiring female models | Statement: [Australia's Next Top Model, contestantEligibility, aspiring female models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contestantEligibility Context triple: [Australia's Next Top Model, contestantEligibility, aspiring female models]
-
A.
typicalPlayerEligibility
Indicates that an entity meets the usual or standard conditions required to be eligible to participate as a player in a given context.
-
B.
controlsPlayerEligibility
Indicates a relationship where one entity determines or regulates whether a player is allowed to participate.
-
C.
eligibilityLevel
Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
-
D.
eligibility
chosen
Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
-
E.
playerEligibilityBasis
Indicates the basis or criteria used to determine a player's eligibility for participation.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 6:29 p.m.