Triple
T7560661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgan |
E178785
|
entity |
| Predicate | isAssociatedWith |
P2830
|
FINISHED |
| Object | Morgan (surname) |
E459318
|
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: Morgan (surname) | Statement: [Morgan, isAssociatedWith, Morgan (surname)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Morgan (surname) Context triple: [Morgan, isAssociatedWith, Morgan (surname)]
-
A.
Morgan family
The Morgan family is a prominent American banking dynasty best known for its role in founding and leading the House of Morgan financial empire.
-
B.
Morgan
Morgan is the middle name of the renowned English novelist and essayist E. M. Forster.
-
C.
Morgan
chosen
Morgan is a common English surname borne by numerous notable individuals across fields such as science, finance, and entertainment.
-
D.
Morgan
Morgan is the second-generation core design used in AMD's Duron processors, featuring improvements in performance and efficiency over the original Spitfire core.
-
E.
Morgan
Morgan is a residential neighborhood within the borough of Sayreville in Middlesex County, New Jersey.
- 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_69c69f2f80288190b95cceb4da92ab2b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f8dd96488190b4cca25ae8f7f95c |
completed | March 27, 2026, 9:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c856cc869081909555ae03dec52288 |
completed | March 28, 2026, 10:31 p.m. |
Created at: March 27, 2026, 3:50 p.m.