Triple
T16848028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R.J. MacReady |
E409594
|
entity |
| Predicate | hasCompanionCharacter |
P22642
|
FINISHED |
| Object | Fuchs |
E172853
|
NE 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: Fuchs | Statement: [R.J. MacReady, hasCompanionCharacter, Fuchs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fuchs Context triple: [R.J. MacReady, hasCompanionCharacter, Fuchs]
-
A.
Fuchs
chosen
Fuchs is a German surname borne by numerous notable individuals across fields such as science, politics, and the arts.
-
B.
Fuhse
Fuhse is a river in Lower Saxony, Germany, that flows through several towns before joining the Aller River.
-
C.
Fiser
Fiser is a surname variant of Fischer, commonly associated with Central or Eastern European origins.
-
D.
Fagel
Fagel is a Dutch surname historically associated with a prominent family of statesmen and diplomats, including Gaspar Fagel.
-
E.
Fuscherkarkopf
Fuscherkarkopf is a prominent alpine peak in the Austrian Alps, known for its high elevation and location within the Glockner Group of the Hohe Tauern range.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b376bac48190ae09f29a28c55f8c |
completed | April 18, 2026, 4:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb1d555c8190883c82e562b7bfe9 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:24 a.m.