Triple
T8320876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gregor |
E194828
|
entity |
| Predicate | associatedFieldOfNotableBearer |
P2531
|
FINISHED |
| Object | genetics |
—
|
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: genetics | Statement: [Gregor, associatedFieldOfNotableBearer, genetics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedFieldOfNotableBearer Context triple: [Gregor, associatedFieldOfNotableBearer, genetics]
-
A.
hasNotableFieldOfBearers
chosen
Indicates that the entities share a significant or distinguished area of activity, expertise, or achievement associated with their bearers.
-
B.
associatedWithNotableBearerNationality
Indicates that an entity is connected to the nationality of a notable bearer of a related name or title.
-
C.
notableBearerFullName
Indicates that a full personal name is that of a notable or well-known bearer associated with the referenced entity.
-
D.
associatedWithRoleOfNameBearer
Indicates that an entity is connected to or involved with the specific role or function held by a designated name bearer.
-
E.
notableBearerDescription
Indicates that the subject has a notable bearer, with the object providing a textual description of that bearer’s significance or identity.
- 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_69ca82e7a8a88190a32bb5cc0feb012d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f67aee88190b245f8d6e57a40b2 |
completed | March 31, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69cb70bf689c8190a9d9b6b872abf53d |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:55 p.m.