Triple
T9342574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toho |
E224796
|
entity |
| Predicate | licensesRightsFor |
P12718
|
FINISHED |
| Object | Godzilla character |
—
|
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: Godzilla character | Statement: [Toho, licensesRightsFor, Godzilla character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: licensesRightsFor Context triple: [Toho, licensesRightsFor, Godzilla character]
-
A.
licenseFocus
Indicates that a license specifically targets, applies to, or is primarily concerned with a particular subject, activity, or scope.
-
B.
licenseFor
chosen
Indicates that one entity grants or holds formal permission or authorization for another entity to perform an activity, use a resource, or operate under specified conditions.
-
C.
licenseStewardship
Indicates that one entity is responsible for managing, overseeing, or administering a license on behalf of another entity.
-
D.
licenseBuiltIn
Indicates that a license is inherently included within or comes standard as part of another product, service, or system rather than being added separately.
-
E.
licenseAdvocated
Indicates that an agent publicly supports, recommends, or argues in favor of a particular license being used or adopted.
- 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_69ca842993248190a79ab06968994b86 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4bb11cd08190b159a6066dd0ebf1 |
completed | April 1, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69cc7a66aef08190b8d668cff5b04f5f |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:40 p.m.