Triple
T10459426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count Morano |
E246630
|
entity |
| Predicate | pursuitType |
P60891
|
FINISHED |
| Object | unwanted courtship |
—
|
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: unwanted courtship | Statement: [Count Morano, pursuitType, unwanted courtship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pursuitType Context triple: [Count Morano, pursuitType, unwanted courtship]
-
A.
seekerType
Indicates the specific category or role of the entity that is performing or initiating the seeking action in the relationship.
-
B.
pursuitLocomotive
chosen
Indicates engaging in locomotion specifically aimed at following or chasing another entity.
-
C.
explorationType
Indicates the specific kind or category of exploration activity associated with an entity or event.
-
D.
soughtTo
Indicates that one entity attempted or intended to obtain, achieve, or bring about another entity or outcome.
-
E.
spurType
Indicates the specific kind or category of spur associated with or used by an entity.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe4b6d408190af59104a44871578 |
completed | April 7, 2026, 12:53 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:18 p.m.