Triple
T35809493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terra Ryzing |
E1035190
|
entity |
| Predicate | hasGivenNameOfPerformer |
P98225
|
FINISHED |
| Object | Paul |
—
|
NE NERFINISHED |
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: Paul | Statement: [Terra Ryzing, hasGivenNameOfPerformer, Paul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenNameOfPerformer Context triple: [Terra Ryzing, hasGivenNameOfPerformer, Paul]
-
A.
hasPerformerGivenName
chosen
Indicates that a performer is associated with a specific given (first) name.
-
B.
performerFullName
Indicates the complete name of the entity that performs an action or role in the described context.
-
C.
performerBirthName
Indicates the full name a performer was given at birth, as distinct from any stage or professional name they may use.
-
D.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
-
E.
performingNameDerivedFrom
Indicates that the name used for a performance or performing entity is derived from another name (such as a legal, original, or canonical name).
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aa699d68819081ed363931894ab3 |
completed | May 3, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69f7a8d219f8819081dc4ce3c83ca0cb |
completed | May 3, 2026, 7:58 p.m. |
Created at: May 3, 2026, 4:06 p.m.