Triple
T3895604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fremantle Dockers |
E88162
|
entity |
| Predicate | homeJumperDesign |
P1529
|
FINISHED |
| Object | chevron |
—
|
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: chevron | Statement: [Fremantle Dockers, homeJumperDesign, chevron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeJumperDesign Context triple: [Fremantle Dockers, homeJumperDesign, chevron]
-
A.
homeJumperFeature
Indicates a feature that enables or supports jumping directly to a home or main location within a system or interface.
-
B.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
C.
hasDesign
chosen
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
D.
helpsDesign
Indicates that one entity assists or contributes to another entity’s design or design process.
-
E.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
- 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_69aed9466d548190939f5217a23ed4ac |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.