Triple
T32723416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Davis Cup team |
E836736
|
entity |
| Predicate | captainType |
P174842
|
FINISHED |
| Object | non‑playing captain |
—
|
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: non‑playing captain | Statement: [United States Davis Cup team, captainType, non‑playing captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainType Context triple: [United States Davis Cup team, captainType, non‑playing captain]
-
A.
captain
Indicates that one entity serves as the leader or person in command of another entity, typically a team, group, or vessel.
-
B.
captainSpecies
Indicates that a given species serves as the captain or commanding leader in relation to another entity or context.
-
C.
craftType
Indicates the specific kind or category of craft or vessel associated with an entity.
-
D.
captainInName
Indicates that an entity’s name or title explicitly includes the word “Captain.”
-
E.
coCaptain
Indicates that two or more individuals share the role and responsibilities of captain jointly.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8b484b48190b5c37ba1c3101056 |
completed | May 3, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:11 a.m.