Triple

T33237732
Position Surface form Disambiguated ID Type / Status
Subject 1888 tour of Australia and New Zealand E850876 entity
Predicate organisingTeam P151320 FINISHED
Object combined British team 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: combined British team | Statement: [1888 tour of Australia and New Zealand, organisingTeam, combined British team]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: organisingTeam
Context triple: [1888 tour of Australia and New Zealand, organisingTeam, combined British team]
  • A. organisedWith
    Indicates that two or more entities are arranged, coordinated, or structured together as part of the same organizing context or effort.
  • B. organisedFor
    Indicates that something has been arranged, structured, or coordinated specifically to serve, support, or benefit a particular entity or purpose.
  • C. organizedTeam chosen
    Indicates that an entity has formed, structured, or coordinated a group of individuals to function together as a team.
  • D. oftenOrganizedBy
    Indicates that an event, activity, or process is frequently arranged, coordinated, or hosted by a particular agent or entity.
  • E. organizadoPor
    Indicates that something is arranged, managed, or coordinated by a particular agent or entity.
  • 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_69f349613f988190a1eb75467d167122 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
Created at: May 1, 2026, 1:31 a.m.