Triple
T14525763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 日本国旗 |
E340770
|
entity |
| Predicate | 使用制限 |
P99
|
FINISHED |
| Object | 特段の一般的使用制限はない |
—
|
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: 特段の一般的使用制限はない | Statement: [日本国旗, 使用制限, 特段の一般的使用制限はない]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 使用制限 Context triple: [日本国旗, 使用制限, 特段の一般的使用制限はない]
-
A.
hasLimitation
chosen
Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
-
B.
isLimitOf
Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
-
C.
mayHaveRestriction
Indicates that an entity can be subject to one or more limitations, conditions, or constraints, though such restrictions are not necessarily present.
-
D.
mayRestrictActivity
Indicates that one entity has the authority or ability to limit, constrain, or prohibit certain actions or behaviors of another entity.
-
E.
restrictedFromUseFor
Indicates that something is prohibited or limited from being used for a specified purpose, context, or application.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dea050781881909ed685d94479bf99 |
completed | April 14, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69de5c518fc08190a6ce4d8be05c4c5d |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.