Triple
T6657813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States amateur players |
E151391
|
entity |
| Predicate | maySignWith |
P46678
|
FINISHED |
| Object | Major League Baseball organizations after being drafted |
—
|
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: Major League Baseball organizations after being drafted | Statement: [United States amateur players, maySignWith, Major League Baseball organizations after being drafted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maySignWith Context triple: [United States amateur players, maySignWith, Major League Baseball organizations after being drafted]
-
A.
maySign
Indicates that an entity has the permission or authority to sign a document, agreement, or similar item.
-
B.
canSign
chosen
Indicates that an entity has the authority or capability to sign a document, agreement, or similar item.
-
C.
willSignedOn
Indicates that a person has formally signed a will on a specific date or occasion, thereby validating or executing that testamentary document.
-
D.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
E.
coSignedWith
Indicates that an entity has jointly signed a document, agreement, or obligation together with another 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_69c687f5fac48190a09e4838d9c6b45d |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.