Triple
T7633285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gauss family |
E172810
|
entity |
| Predicate | hasMemberBySurname |
P77449
|
FINISHED |
| Object | people bearing the Gauss surname |
—
|
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: people bearing the Gauss surname | Statement: [Gauss family, hasMemberBySurname, people bearing the Gauss surname]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMemberBySurname Context triple: [Gauss family, hasMemberBySurname, people bearing the Gauss surname]
-
A.
hasComponentSurname
Indicates that an entity’s full name includes a specified surname as one of its component parts.
-
B.
hasNotablePersonWithSurname
Indicates that an entity is associated with at least one notable person who bears a specified surname.
-
C.
hasFamilyNameOf
Indicates that one entity bears or uses the same family name (surname) as another entity.
-
D.
hasMemberFrom
Indicates that a group, organization, or collection includes at least one member originating from or belonging to a specified source, place, or category.
-
E.
hasExampleSurname
Indicates that an entity is associated with a sample or illustrative surname used as an example rather than a real or primary family name.
- F. None of above. chosen
Provenance (4 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_69c69952849881908fdcea7a93bfc307 |
completed | March 27, 2026, 2:50 p.m. |
| NER | Named-entity recognition | batch_69c6faa5f4f08190a7e5259a1b6fb576 |
completed | March 27, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e8cadc8190b7977fcd213954dd |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:57 p.m.