Triple
T37467940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalar |
E931077
|
entity |
| Predicate | hasScientistCharacter |
P151029
|
FINISHED |
| Object | Professor |
—
|
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: Professor | Statement: [Avalar, hasScientistCharacter, Professor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScientistCharacter Context triple: [Avalar, hasScientistCharacter, Professor]
-
A.
hasHumanScientistCharacter
chosen
Indicates that an entity includes or features a character who is a human scientist.
-
B.
hasScientificRole
Indicates that an entity holds or performs a specific scientific position, function, or responsibility in relation to another entity or context.
-
C.
hasScientificLegacy
Indicates that an entity has left a lasting, influential impact on scientific knowledge, methods, or practice that continues beyond its original context or time.
-
D.
typeOfScientist
Indicates that one entity is a scientist and the other specifies the kind or specialization of that scientist.
-
E.
hasScience
Indicates that an entity possesses, includes, or is associated with a particular scientific discipline, content, or attribute.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 3, 2026, 4:17 p.m.