Triple
T25023115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Mansfield |
E626631
|
entity |
| Predicate | relationshipToCockfighting |
P172077
|
FINISHED |
| Object | professional dedication |
—
|
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: professional dedication | Statement: [Frank Mansfield, relationshipToCockfighting, professional dedication]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToCockfighting Context triple: [Frank Mansfield, relationshipToCockfighting, professional dedication]
-
A.
relationshipToPlayer
Indicates the type of personal or social connection an entity has with the player.
-
B.
relationshipToCreature
Indicates a specified type of relational connection that one entity has toward a particular creature.
-
C.
associationWithHumans
Indicates a general relationship, connection, or involvement between an entity and one or more humans.
-
D.
relationshipToEvent
Indicates the specific way an entity is connected or related to a particular event.
-
E.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
- 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_69e2ff28ee3881909c626af002457a4a |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 18, 2026, 6:07 a.m.