Triple
T1397725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australia/Sydney |
E30704
|
entity |
| Predicate | olsonDatabaseIdentifier |
P3732
|
FINISHED |
| Object | Australia/Sydney |
—
|
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: Australia/Sydney | Statement: [Australia/Sydney, olsonDatabaseIdentifier, Australia/Sydney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: olsonDatabaseIdentifier Context triple: [Australia/Sydney, olsonDatabaseIdentifier, Australia/Sydney]
-
A.
OCLC
Indicates that an entity is associated with an OCLC (Online Computer Library Center) control number or record identifier in a bibliographic or library cataloging context.
-
B.
knownFrom
Indicates that one entity is aware of, has learned about, or recognizes another entity through a specified source, context, or medium.
-
C.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
eraName
Indicates the named historical or chronological era associated with an entity or time period.
-
E.
ISNI
Indicates that an entity is associated with a specific International Standard Name Identifier, uniquely identifying its public identity in creative or scholarly activities.
- 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_69a498fd4e408190bd73eca30ea9754c |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c382b6588190833c39ac84fb6139 |
completed | March 1, 2026, 10:53 p.m. |
| PD | Predicate disambiguation | batch_69a4bf017f8081908572121560ec621f |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.