Triple
T29641462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giuseppe Ferlini (tomb treasures) |
E755871
|
entity |
| Predicate | hasDiscovererOccupation |
P94584
|
FINISHED |
| Object | Italian explorer |
—
|
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: Italian explorer | Statement: [Giuseppe Ferlini (tomb treasures), hasDiscovererOccupation, Italian explorer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDiscovererOccupation Context triple: [Giuseppe Ferlini (tomb treasures), hasDiscovererOccupation, Italian explorer]
-
A.
isDiscoveredBy
Indicates that something (such as an object, fact, or phenomenon) is found, identified, or revealed by a particular agent or entity.
-
B.
knownForDiscovering
Indicates that one entity is recognized or notable for having discovered another entity.
-
C.
discovererRole
chosen
Indicates the role or capacity in which an entity participates as the discoverer of something.
-
D.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
E.
hasDiscovered
Indicates that one entity has found, detected, or uncovered the existence, presence, or truth of another entity or phenomenon.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 28, 2026, 6:47 p.m.