Triple
T37717470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lev Gleason Publications |
E939494
|
entity |
| Predicate | creativeCollaborators |
P7732
|
FINISHED |
| Object | Charles Biro |
—
|
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: Charles Biro | Statement: [Lev Gleason Publications, creativeCollaborators, Charles Biro]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creativeCollaborators Context triple: [Lev Gleason Publications, creativeCollaborators, Charles Biro]
-
A.
partnerInArtisticCollaboration
Indicates that two or more entities are engaged together as partners in a shared artistic collaboration or creative project.
-
B.
creativeContributor
Indicates a relationship where an entity plays an active role in originating, designing, or shaping the creative content or form of another entity.
-
C.
designerCollaboratedWith
Indicates that a designer worked together with another party on a shared project or creative endeavor.
-
D.
coCreator
chosen
Indicates that two or more entities jointly created or produced something together.
-
E.
creativeFieldPeers
Indicates that two entities are peers or counterparts within the same or closely related creative field or discipline.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:18 p.m.