Triple
T26254465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thompson group Th |
E656680
|
entity |
| Predicate | hasAtlasNotation |
P138097
|
FINISHED |
| Object | Th |
—
|
NE NERFINISHED |
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: Th | Statement: [Thompson group Th, hasAtlasNotation, Th]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAtlasNotation Context triple: [Thompson group Th, hasAtlasNotation, Th]
-
A.
hasAtlasName
Indicates that an entity is associated with a specific name as recorded in an atlas or standardized geographic reference.
-
B.
usesNotationFor
Indicates that one entity employs or adopts a particular notation system or symbolic representation for another entity.
-
C.
hasNameInNotation
chosen
Indicates that an entity is referred to by a specific name or label within a particular notation or symbolic system.
-
D.
hasAlternativeNotation
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
E.
hasObjectNotation
Indicates that an entity is represented or expressed using a specific object-based notation or symbolic format.
- 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_69ee5b4d25ac819086acb51184602576 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60dcd2e688190b54e36b0ff0d9187 |
completed | May 2, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:08 p.m.